From: darrick.wong@oracle.com (Darrick J. Wong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] mm: Make snapshotting pages for stable writes a per-bio operation
Date: Tue, 9 Apr 2013 11:03:52 -0700 [thread overview]
Message-ID: <20130409180352.GA8907@blackbox.djwong.org> (raw)
In-Reply-To: <20130403144244.GC14667@quack.suse.cz>
On Wed, Apr 03, 2013 at 04:42:44PM +0200, Jan Kara wrote:
> On Wed 03-04-13 15:20:19, Mel Gorman wrote:
> > On Tue, Apr 02, 2013 at 10:01:43AM -0700, Darrick J. Wong wrote:
> > > Hi,
> > >
> > > A couple of weeks have gone by without further comments about this patch.
> > >
> > > Are you interested in the minor cleanups and added comments, or is the v2 patch
> > > in -next good enough?
> > >
> > > Apparently Mel Gorman's interested in this patchset too. Mel: Most of stable
> > > pages part 2 are already in upstream for 3.9... except this piece. Are you
> > > interested in having this piece in 3.9 also? Or is 3.10 good enough for
> > > everyone?
> > >
> >
> > My understanding is that it only affects ARM and DEBUG_VM so there is a
> > relatively small chance of this generating spurious bug reports. However,
> > 3.9 is still far enough away that I see no good reason to delay this patch
> > until 3.10 either.
> No, actually with direct IO, anything that needs stable pages is going to
> blow up quickly because pages attached to bio needn't be from page cache. So
> I think it should better make it into 3.9.
Hmm. The previous version of this patch has been hanging around in -next for a
few weeks without problems (afaik). With just a raw 3.9-rc[56] I haven't been
able to produce a failed checksum or kernel crash when running with O_DIRECT,
either with the write-after-checksum reproducer or even a simple dd
oflag=direct. But maybe I've gotten lucky on x86?
So... Andrew: Would you like to pick up the patch with more descriptive
comments? And, is it too late to push it for 3.9? Jan seems to think we might
have a bug (though I haven't encountered it).
I'll resend the patch just in case it got eaten.
--D
>
> Honza
> --
> Jan Kara <jack@suse.cz>
> SUSE Labs, CR
next prev parent reply other threads:[~2013-04-09 18:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5139DB90.5090302@gmail.com>
2013-03-12 22:32 ` [PATCH] bounce:fix bug, avoid to flush dcache on slab page from jbd2 Andrew Morton
2013-03-13 1:10 ` Darrick J. Wong
2013-03-13 3:35 ` Shuge
2013-03-13 4:11 ` Andrew Morton
2013-03-13 9:42 ` Russell King - ARM Linux
2013-03-13 8:50 ` Jan Kara
2013-03-13 19:44 ` Darrick J. Wong
2013-03-13 21:02 ` Jan Kara
2013-03-14 22:42 ` Darrick J. Wong
2013-03-14 23:01 ` Andrew Morton
2013-03-15 10:01 ` Jan Kara
2013-03-15 17:54 ` Darrick J. Wong
2013-03-18 17:32 ` Jan Kara
2013-03-15 23:28 ` [PATCH] mm: Make snapshotting pages for stable writes a per-bio operation Darrick J. Wong
2013-03-18 17:41 ` Jan Kara
2013-03-18 23:01 ` Darrick J. Wong
2013-03-18 23:02 ` [PATCH v3] " Darrick J. Wong
2013-03-19 8:54 ` Jan Kara
2013-04-02 17:01 ` Darrick J. Wong
2013-04-03 14:20 ` Mel Gorman
2013-04-03 14:42 ` Jan Kara
2013-04-09 18:03 ` Darrick J. Wong [this message]
2013-03-14 22:46 ` [PATCH] bounce:fix bug, avoid to flush dcache on slab page from jbd2 Andrew Morton
2013-03-14 23:27 ` 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=20130409180352.GA8907@blackbox.djwong.org \
--to=darrick.wong@oracle.com \
--cc=linux-arm-kernel@lists.infradead.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).