From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-xfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfs: for-next branch updated to 800b269
Date: Tue, 30 Aug 2016 09:23:08 +1000 [thread overview]
Message-ID: <20160829232308.GQ19025@dastard> (raw)
In-Reply-To: <20160829145249.GF22760@birch.djwong.org>
On Mon, Aug 29, 2016 at 07:52:49AM -0700, Darrick J. Wong wrote:
> On Mon, Aug 29, 2016 at 11:31:12AM +1000, Dave Chinner wrote:
> > On Fri, Aug 26, 2016 at 12:48:44AM -0700, Christoph Hellwig wrote:
> > > Hi Dave,
> > >
> > > please consider: "[PATCH] iomap: don't set FIEMAP_EXTENT_MERGED for
> > > extent based filesystems"
> > >
> > > for 4.8. It fixes a regression in the iomap-based fiemap
> > > implementation, and it's fairly trivial as well.
> >
> > Oh, damn, I thought I got that one. I'll append it to the
> > series and push it out.
>
> It might be a good idea to pick up "xfs: track log done items directly
> in the deferred pending work item" too, if it fixes the slab
> corruptions that Christoph reported.
Doesn't apply cleanly to the 4.8 tree, and the xfs_defer_finish()
code is quite different, so you'll need to rebase and resend that
patch if you think it needs to be applied to the 4.8-rc kernel.
I can always send it to Linus later.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-08-29 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 6:25 [ANNOUNCE] xfs: for-next branch updated to 800b269 Dave Chinner
2016-08-26 7:48 ` Christoph Hellwig
2016-08-29 1:31 ` Dave Chinner
2016-08-29 14:52 ` Darrick J. Wong
2016-08-29 23:23 ` Dave Chinner [this message]
2016-08-30 3:40 ` Darrick J. Wong
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=20160829232308.GQ19025@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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