From: Kent Overstreet <kent.overstreet@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Jan Kara <jack@suse.cz>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
axboe@fb.com, Linux FS Devel <linux-fsdevel@vger.kernel.org>,
zab@zabbo.net, linux-btrfs@vger.kernel.org
Subject: Re: [dm-devel] Proposal for annotating _unstable_ pages
Date: Fri, 22 May 2015 11:33:04 -0700 [thread overview]
Message-ID: <20150522183304.GB27397@kmo-pixel> (raw)
In-Reply-To: <20150522181759.GB32090@birch.djwong.org>
On Fri, May 22, 2015 at 11:17:59AM -0700, Darrick J. Wong wrote:
> Back when I was writing the stable pages patches, I observed that some of the
> filesystems didn't hold the pages containing their own metadata stable during
> writeback on a stable-writes device. The journalling filesystems were fine
> because they had various means to take care of that.
>
> ISTR ext2 and vfat were the biggest culprits, but both maintainers rejected
> the patches to fix that behavior. This might no longer be the case; those
> patches were so long ago I can't find them in Google.
Not at all surprised. Yeah, this would solve that problem - we just annotate
those bios so we don't bounce them until we hit a point where we need to.
prev parent reply other threads:[~2015-05-22 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 20:58 Let's get a File & Storage miniconf going at LPC2015! Darrick J. Wong
2015-05-19 15:42 ` Kent Overstreet
2015-05-19 20:10 ` Darrick J. Wong
2015-05-21 1:04 ` Proposal for annotating _unstable_ pages Kent Overstreet
2015-05-21 16:54 ` Jan Kara
2015-05-21 18:09 ` Kent Overstreet
2015-05-21 19:21 ` Jan Kara
2015-05-22 18:17 ` [dm-devel] " Darrick J. Wong
2015-05-22 18:33 ` Kent Overstreet [this message]
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=20150522183304.GB27397@kmo-pixel \
--to=kent.overstreet@gmail.com \
--cc=axboe@fb.com \
--cc=darrick.wong@oracle.com \
--cc=dm-devel@redhat.com \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=zab@zabbo.net \
/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).