public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/3] xfs: evict all inodes involved with log redo item recovery
Date: Fri, 11 Aug 2017 09:51:36 -0700	[thread overview]
Message-ID: <20170811165136.GD24087@magnolia> (raw)
In-Reply-To: <20170811112203.GC27964@infradead.org>

On Fri, Aug 11, 2017 at 04:22:03AM -0700, Christoph Hellwig wrote:
> On Thu, Aug 10, 2017 at 10:18:51AM -0700, Darrick J. Wong wrote:
> > I felt there's less messing around with vfs internals by sticking to
> > igrab and iput (and letting them deal with the internal inode state)
> > since that's what xfs uses elsewhere to manage inode life cycles.
> 
> I'd feel much safer calling evict_inodes rather than reimplementing
> it poorly.  In fact we might want to just call it in the VFS after
> a failed mount?

I don't think we can call it in the vfs after a failed mount since by
that time we've pulled down all the fs-specific stuff by then, right?

In any case I think it's only xfs that needs this, since (afaict) the
ones I looked at don't set MS_ACTIVE in fill_super and have a small
set of inodes that they explicitly iget and iput.

> Either way please also add Al to the Cc for the next version.

Ok.

--D

> --
> 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

  reply	other threads:[~2017-08-11 16:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10  5:23 [PATCH 1/3] xfs: clear MS_ACTIVE after finishing log recovery to avoid inode leak Darrick J. Wong
2017-08-10  5:23 ` [PATCH 2/3] xfs: evict all inodes involved with log redo item recovery Darrick J. Wong
2017-08-10 14:51   ` Brian Foster
2017-08-10 17:18     ` Darrick J. Wong
2017-08-10 17:54       ` Brian Foster
2017-08-11 11:22       ` Christoph Hellwig
2017-08-11 16:51         ` Darrick J. Wong [this message]
2017-08-11 19:50   ` [PATCH v2 " Darrick J. Wong
2017-08-11 23:42     ` Dave Chinner
2017-08-11 23:59       ` Darrick J. Wong
2017-08-10  5:23 ` [PATCH 3/3] xfs: don't leak quotacheck dquots when cow recovery fails Darrick J. Wong
2017-08-10 14:51   ` Brian Foster
2017-08-11 11:19   ` Christoph Hellwig
2017-08-11 19:48   ` [PATCH v3 " Darrick J. Wong
2017-08-14 12:40     ` Brian Foster
2017-08-10 18:15 ` [PATCH 1/3] xfs: clear MS_ACTIVE after finishing log recovery to avoid inode leak Allison Henderson
2017-08-11 11:13 ` Christoph Hellwig

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=20170811165136.GD24087@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=bfoster@redhat.com \
    --cc=hch@infradead.org \
    --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