From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Brian Foster <bfoster@redhat.com>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH v2] xfs: move the inline directory verifiers
Date: Thu, 30 Mar 2017 09:41:10 +1100 [thread overview]
Message-ID: <20170329224110.GL17542@dastard> (raw)
In-Reply-To: <20170329182156.GC4864@birch.djwong.org>
On Wed, Mar 29, 2017 at 11:21:57AM -0700, Darrick J. Wong wrote:
> On Tue, Mar 28, 2017 at 01:24:44PM -0400, Brian Foster wrote:
> > On Tue, Mar 28, 2017 at 11:11:05AM -0400, Brian Foster wrote:
> > > On Tue, Mar 28, 2017 at 08:00:47AM -0700, Darrick J. Wong wrote:
> > > > On Tue, Mar 28, 2017 at 08:51:05AM -0400, Brian Foster wrote:
> > > > > On Mon, Mar 27, 2017 at 04:03:15PM -0700, Darrick J. Wong wrote:
> > > > > > The inline directory verifiers should be called on the inode fork data,
> > > > > > which means after iformat_local on the read side, and prior to
> > > > > > ifork_flush on the write side. This makes the fork verifier more
> > > > > > consistent with the way buffer verifiers work -- i.e. they will operate
> > > > > > on the memory buffer that the code will be reading and writing directly.
> > > > > >
> > > > > > Also revise the verifier function to return -EFSCORRUPTED so that we
> > > > > > don't flood the logs with corruption messages and assert notices.
> > > > > >
> > > > > > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> > > > > > ---
> > > > > > v2: get the inode d_ops the proper way
> > > > > > ---
> > > > >
> > > > > What does this apply against?
> > > >
> > > > It ought to apply against the previous inline dir verifier patch.
> > > >
> > >
> > > Hm, doesn't apply against [1] for me. Care to just repost these as a
> > > series if the dependent code hasn't been merged yet?
> > >
> > > Brian
> > >
> > > [1] https://patchwork.kernel.org/patch/9626859/
> > >
> >
> > I lost track of the fact that the first patch went into -rc and thus
> > confused myself over where this should apply. This applies to 4.11.0-rc4
> > and looks fine to me:
>
> Does anyone have a problem if I send this to Linus for 4.11-rc5?
> I'd rather atone for my sins sooner than later. :)
There's no urgency required here - it's just a cleanup patch. The
code in the tree works fine, so why risk adding regressions
at a late stage? Just add it to the for-next queue and let it soak
until the merge window.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-03-29 22:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 23:03 [PATCH v2] xfs: move the inline directory verifiers Darrick J. Wong
2017-03-28 12:51 ` Brian Foster
2017-03-28 15:00 ` Darrick J. Wong
2017-03-28 15:11 ` Brian Foster
2017-03-28 17:24 ` Brian Foster
2017-03-29 18:21 ` Darrick J. Wong
2017-03-29 18:52 ` Brian Foster
2017-03-29 22:41 ` Dave Chinner [this message]
2017-03-31 16:07 ` Christoph Hellwig
2017-03-31 16:24 ` Darrick J. Wong
2017-03-31 16:28 ` Christoph Hellwig
2017-03-31 16:38 ` Darrick J. Wong
2017-03-31 16:40 ` Christoph Hellwig
2017-04-01 23:17 ` Dave Chinner
2017-03-31 17:24 ` 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=20170329224110.GL17542@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.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).