From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Eryu Guan <eguan@redhat.com>, Miklos Szeredi <miklos@szeredi.hu>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH] xfs: preserve i_rdev when recycling a reclaimable inode
Date: Thu, 25 Jan 2018 13:30:40 -0800 [thread overview]
Message-ID: <20180125213040.GO9068@magnolia> (raw)
In-Reply-To: <1516915298-8886-1-git-send-email-amir73il@gmail.com>
On Thu, Jan 25, 2018 at 11:21:38PM +0200, Amir Goldstein wrote:
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
>
> Darrick,
>
> This patch fixes a problem I am hitting consistenty with xfstest
> overlay/017 with certain overlay mount options (index=on,nfs_export=off).
>
> I see that overlayfs looks up in underlying xfs and gets a chardev
> or blockdev inode with non initialized i_rdev (these are not whiteout
> inodes).
>
> It takes a certain timing which happens in this test that does lookup
> immediately after drop caches. The test causes a permanent error in
> inode cache of xfs that is only fixed after another drop caches or
> cycle mount.
>
> So I am certain there is a problem and that this patch fixes the
> problem, I'm just not sure this is the right fix and if it is, which
> is the commit that it "Fixes".
We're basically reinitializing a VFS inode that was on its way to being
reclaimed, which means that we don't xfs_iread. We still have to
reinitialize the vfs inode state (because we'd already torn that down),
so we have to preserve all the vfs inode state that the xfs inode stores
in the vfs inode.
Oh, right, hch moved if_rdev to i_rdev in 66f364649d870 ("xfs: remove
if_rdev") but forgot the xfs_reinit_inode usage. so that would be the
commit that this fixes. Doh.
--D
>
> Thanks,
> Amir.
>
> fs/xfs/xfs_icache.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/xfs/xfs_icache.c b/fs/xfs/xfs_icache.c
> index 3861d61fb265..3ce946063ffe 100644
> --- a/fs/xfs/xfs_icache.c
> +++ b/fs/xfs/xfs_icache.c
> @@ -295,6 +295,7 @@ xfs_reinit_inode(
> uint32_t generation = inode->i_generation;
> uint64_t version = inode->i_version;
> umode_t mode = inode->i_mode;
> + dev_t dev = inode->i_rdev;
>
> error = inode_init_always(mp->m_super, inode);
>
> @@ -302,6 +303,7 @@ xfs_reinit_inode(
> inode->i_generation = generation;
> inode->i_version = version;
> inode->i_mode = mode;
> + inode->i_rdev = dev;
> return error;
> }
>
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-25 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 21:21 [RFC][PATCH] xfs: preserve i_rdev when recycling a reclaimable inode Amir Goldstein
2018-01-25 21:30 ` Darrick J. Wong [this message]
2018-01-26 6:51 ` Amir Goldstein
2018-01-26 7:13 ` Darrick J. Wong
2018-01-26 7:44 ` Amir Goldstein
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=20180125213040.GO9068@magnolia \
--to=darrick.wong@oracle.com \
--cc=amir73il@gmail.com \
--cc=eguan@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).