On Mon, Oct 03, 2016 at 05:29:25PM -0700, Darrick J. Wong wrote:
> On Mon, Oct 03, 2016 at 03:04:10PM -0400, Brian Foster wrote:
> > On Thu, Sep 29, 2016 at 08:08:17PM -0700, Darrick J. Wong wrote:
> > > Log recovery will iget an inode to replay BUI items and iput the inode
> > > when it's done. Unfortunately, the iput will see that i_nlink == 0
> > > and decide to truncate & free the inode, which prevents us from
> > > replaying subsequent BUIs. We can't skip the BUIs because we have to
> > > replay all the redo items to ensure that atomic operations complete.
> > >
...
> >
> > > Since unlinked inode recovery will reap the inode anyway, we can
> > > safely introduce a new inode flag to indicate that an inode is in this
> > > 'unlinked recovery' state and should not be auto-reaped in the
> > > drop_inode path.
> > >
> > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx>
> > > ---
> > > fs/xfs/xfs_bmap_item.c | 1 +
> > > fs/xfs/xfs_inode.c | 8 ++++++++
> > > fs/xfs/xfs_inode.h | 6 ++++++
> > > fs/xfs/xfs_log_recover.c | 1 +
> > > 4 files changed, 16 insertions(+)
> > >
> > >
...
> > > diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> > > index e08eaea..0c25a76 100644
> > > --- a/fs/xfs/xfs_inode.c
> > > +++ b/fs/xfs/xfs_inode.c
> > > @@ -1855,6 +1855,14 @@ xfs_inactive(
> > > if (mp->m_flags & XFS_MOUNT_RDONLY)
> > > return;
> > >
> > > + /*
> > > + * If this unlinked inode is in the middle of recovery, don't
> > > + * truncate and free the inode just yet; log recovery will take
> > > + * care of that. See the comment for this inode flag.
> > > + */
> > > + if (xfs_iflags_test(ip, XFS_IRECOVER_UNLINKED))
> > > + return;
> > > +
> >
> > Also, it might be better to push this one block of code down since the
> > following block still deals with i_nlink > 0 properly (not that it will
> > likely affect the code as it is now, since we only handle eofblocks
> > trimming atm).
>
> I put the jump-out case there so that we touch the inode's bmap as little
> as possible while we're recovering the inode. Since the inode is still
> around in memory, so we'll end up back there at a later point anyway.
>
I'm not quite following... it looks like we set the reclaim tag on the
inode unconditionally after we get through xfs_inactive(). That implies
the in-memory inode can go away at any point thereafter, unless somebody
else comes along and happens to look for it. Hmm?
Brian
> --D
>
> >
> > Brian
> >
> > > if (VFS_I(ip)->i_nlink != 0) {
> > > /*
> > > * force is true because we are evicting an inode from the
> > > diff --git a/fs/xfs/xfs_inode.h b/fs/xfs/xfs_inode.h
> > > index a8658e6..46632f1 100644
> > > --- a/fs/xfs/xfs_inode.h
> > > +++ b/fs/xfs/xfs_inode.h
> > > @@ -222,6 +222,12 @@ static inline bool xfs_is_reflink_inode(struct xfs_inode *ip)
> > > #define XFS_IPINNED (1 << __XFS_IPINNED_BIT)
> > > #define XFS_IDONTCACHE (1 << 9) /* don't cache the inode long term */
> > > #define XFS_IEOFBLOCKS (1 << 10)/* has the preallocblocks tag set */
> > > +/*
> > > + * If this unlinked inode is in the middle of recovery, don't let drop_inode
> > > + * truncate and free the inode. This can happen if we iget the inode during
> > > + * log recovery to replay a bmap operation on the inode.
> > > + */
> > > +#define XFS_IRECOVER_UNLINKED (1 << 11)
> > >
> > > /*
> > > * Per-lifetime flags need to be reset when re-using a reclaimable inode during
> > > diff --git a/fs/xfs/xfs_log_recover.c b/fs/xfs/xfs_log_recover.c
> > > index 9697e94..b121f02 100644
> > > --- a/fs/xfs/xfs_log_recover.c
> > > +++ b/fs/xfs/xfs_log_recover.c
> > > @@ -4969,6 +4969,7 @@ xlog_recover_process_one_iunlink(
> > > if (error)
> > > goto fail_iput;
> > >
> > > + xfs_iflags_clear(ip, XFS_IRECOVER_UNLINKED);
> > > ASSERT(VFS_I(ip)->i_nlink == 0);
> > > ASSERT(VFS_I(ip)->i_mode != 0);
> > >
> > >
> > > --
> > > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> > > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > > More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
