Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <CAB9dFdvzTx3tn=z=he08_+QrpnaPsXQ5qWTGyu65Tv7cy2=L1w@mail.gmail.com>
References: <20180724064929.GD19722@shao2-debian> <20180724130155.20641-1-mszeredi@redhat.com>
 <CAB9dFdvzTx3tn=z=he08_+QrpnaPsXQ5qWTGyu65Tv7cy2=L1w@mail.gmail.com>
From:   Marc Dionne <marc.c.dionne@gmail.com>
Date:   Wed, 22 Aug 2018 18:46:36 -0300
Message-ID: <CAB9dFdt=Wf8ZkJV-eqjgqDKzxat2Dq7FoHvGL+GR0DBMKJX8NA@mail.gmail.com>
Subject: Re: [PATCH v3] vfs: don't evict uninitialized inode
To:     Miklos Szeredi <mszeredi@redhat.com>
Cc:     Al Viro <viro@zeniv.linux.org.uk>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-fsdevel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Aug 22, 2018 at 4:37 PM, Marc Dionne <marc.c.dionne@gmail.com> wrote:
>
> FYI with this patch (now merged) I'm seeing warnings whenever an
> object is created in an overlayfs mount:
>
> [  842.152673] list_add double add: new=ffff88017efe03d8,
> prev=ffff88015c07ad88, next=ffff88017efe03d8.
> [  842.152687] WARNING: CPU: 4 PID: 7592 at lib/list_debug.c:31
> __list_add_valid+0x6e/0x80
>

And I see that's now fixed by 6faf05c2b2b4 ("ovl: set I_CREATING on
inode being created").

Marc