From: "Darrick J. Wong" <djwong@kernel.org>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com
Subject: Re: [PATCH 2/3] xfs: drop IDONTCACHE on inodes when we mark them sick
Date: Thu, 3 Jun 2021 13:48:45 -0700 [thread overview]
Message-ID: <20210603204845.GA26380@locust> (raw)
In-Reply-To: <YLjJuZQ0xVk17Dcg@bfoster>
On Thu, Jun 03, 2021 at 08:23:21AM -0400, Brian Foster wrote:
> On Wed, Jun 02, 2021 at 08:12:46PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > When we decide to mark an inode sick, clear the DONTCACHE flag so that
> > the incore inode will be kept around until memory pressure forces it out
> > of memory. This increases the chances that the sick status will be
> > caught by someone compiling a health report later on.
> >
> > Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> > ---
> > fs/xfs/xfs_health.c | 5 +++++
> > fs/xfs/xfs_icache.c | 3 ++-
> > 2 files changed, 7 insertions(+), 1 deletion(-)
> >
> >
> > diff --git a/fs/xfs/xfs_health.c b/fs/xfs/xfs_health.c
> > index 8e0cb05a7142..824e0b781290 100644
> > --- a/fs/xfs/xfs_health.c
> > +++ b/fs/xfs/xfs_health.c
> > @@ -231,6 +231,11 @@ xfs_inode_mark_sick(
> > ip->i_sick |= mask;
> > ip->i_checked |= mask;
> > spin_unlock(&ip->i_flags_lock);
> > +
> > + /* Keep this inode around so we don't lose the sickness report. */
> > + spin_lock(&VFS_I(ip)->i_lock);
> > + VFS_I(ip)->i_state &= ~I_DONTCACHE;
> > + spin_unlock(&VFS_I(ip)->i_lock);
>
> If I follow the scrub code correctly, it will grab a dontcache reference
> on the inode, so presumably the intent here is to clear that status once
> we've identified some problem to keep the inode around. Seems
> reasonable.
<nod> I'll expand the comment:
/*
* Keep this inode around so we don't lose the sickness report.
* Scrub grabs inodes with DONTCACHE assuming that most inode
* are ok, which is not the case here.
*/
>
> > }
> >
> > /* Mark parts of an inode healed. */
> > diff --git a/fs/xfs/xfs_icache.c b/fs/xfs/xfs_icache.c
> > index c3f912a9231b..0e2b6c05e604 100644
> > --- a/fs/xfs/xfs_icache.c
> > +++ b/fs/xfs/xfs_icache.c
> > @@ -23,6 +23,7 @@
> > #include "xfs_dquot.h"
> > #include "xfs_reflink.h"
> > #include "xfs_ialloc.h"
> > +#include "xfs_health.h"
> >
> > #include <linux/iversion.h>
> >
> > @@ -648,7 +649,7 @@ xfs_iget_cache_miss(
> > * time.
> > */
> > iflags = XFS_INEW;
> > - if (flags & XFS_IGET_DONTCACHE)
> > + if ((flags & XFS_IGET_DONTCACHE) && xfs_inode_is_healthy(ip))
> > d_mark_dontcache(VFS_I(ip));
>
> This one I'm less clear on.. we've just allocated ip above and haven't
> made it accessible yet. What's the use case for finding an unhealthy
> inode here?
Hm. I think I went overboard looking for DONTCACHE here, and it doesn't
make any sense to make this change. Ok, dropped.
--D
>
> Brian
>
> > ip->i_udquot = NULL;
> > ip->i_gdquot = NULL;
> >
>
next prev parent reply other threads:[~2021-06-03 20:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 3:12 [PATCHSET v2 0/3] xfs: preserve inode health reports for longer Darrick J. Wong
2021-06-03 3:12 ` [PATCH 1/3] xfs: only reset incore inode health state flags when reclaiming an inode Darrick J. Wong
2021-06-03 4:21 ` Dave Chinner
2021-06-03 20:41 ` Darrick J. Wong
2021-06-03 12:22 ` Brian Foster
2021-06-03 20:41 ` Darrick J. Wong
2021-06-03 3:12 ` [PATCH 2/3] xfs: drop IDONTCACHE on inodes when we mark them sick Darrick J. Wong
2021-06-03 4:34 ` Dave Chinner
2021-06-03 20:49 ` Darrick J. Wong
2021-06-03 12:23 ` Brian Foster
2021-06-03 20:48 ` Darrick J. Wong [this message]
2021-06-03 3:12 ` [PATCH 3/3] xfs: don't let background reclaim forget sick inodes Darrick J. Wong
2021-06-03 4:42 ` Dave Chinner
2021-06-03 12:31 ` Brian Foster
2021-06-03 21:30 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2021-06-06 17:54 [PATCHSET v3 0/3] xfs: preserve inode health reports for longer Darrick J. Wong
2021-06-06 17:54 ` [PATCH 2/3] xfs: drop IDONTCACHE on inodes when we mark them sick Darrick J. Wong
2021-06-07 1:40 ` Dave Chinner
2021-06-08 14:59 ` Carlos Maiolino
2021-06-08 15:21 ` Darrick J. Wong
2021-06-09 8:55 ` Carlos Maiolino
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=20210603204845.GA26380@locust \
--to=djwong@kernel.org \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/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).