From: Marc Dionne <marc.c.dionne@gmail.com>
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
Subject: Re: [PATCH v3] vfs: don't evict uninitialized inode
Date: Wed, 22 Aug 2018 18:46:36 -0300 [thread overview]
Message-ID: <CAB9dFdt=Wf8ZkJV-eqjgqDKzxat2Dq7FoHvGL+GR0DBMKJX8NA@mail.gmail.com> (raw)
In-Reply-To: <CAB9dFdvzTx3tn=z=he08_+QrpnaPsXQ5qWTGyu65Tv7cy2=L1w@mail.gmail.com>
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
prev parent reply other threads:[~2018-08-23 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180724064929.GD19722@shao2-debian>
2018-07-24 13:01 ` [PATCH v3] vfs: don't evict uninitialized inode Miklos Szeredi
2018-08-22 19:37 ` Marc Dionne
2018-08-22 21:46 ` Marc Dionne [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAB9dFdt=Wf8ZkJV-eqjgqDKzxat2Dq7FoHvGL+GR0DBMKJX8NA@mail.gmail.com' \
--to=marc.c.dionne@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).