From: NeilBrown <neilb@suse.de>
To: "Kwolek, Adam" <adam.kwolek@intel.com>
Cc: "Wojcik, Krzysztof" <krzysztof.wojcik@intel.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] Fix over-zealous flush_disk when changing device size.
Date: Wed, 23 Feb 2011 21:01:00 +1100 [thread overview]
Message-ID: <20110223210100.6d8b95f7@notabene.brown> (raw)
In-Reply-To: <905EDD02F158D948B186911EB64DB3D178FAB804@irsmsx503.ger.corp.intel.com>
On Wed, 23 Feb 2011 08:48:09 +0000 "Kwolek, Adam" <adam.kwolek@intel.com>
wrote:
> > > This regression was introduced by commit 608aeef17a
> > > which causes check_disk_size_change to call
> > > flush_disk.
> >
> > This makes sense to me. Nice write-up, Neil.
> >
> > Acked-by: Jeff Moyer <jmoyer@redhat.com>
>
>
> Neil, Is this fix is ready? If yes, where can I find it?
http://neil.brown.name/git?p=md;a=commitdiff;h=a12b63b6f3f60736aace22259a076dfc0ad84b4a
I'll probably submit it to Linus tomorrow. Whether or not he accepts it is
a different question - it is not specific to md so he will probably review it
more closely (at least I will ask him to).
NeilBrown
next prev parent reply other threads:[~2011-02-23 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 5:50 [PATCH] Fix over-zealous flush_disk when changing device size NeilBrown
2011-02-17 17:03 ` Jeff Moyer
2011-02-23 8:48 ` Kwolek, Adam
2011-02-23 10:01 ` NeilBrown [this message]
2011-02-21 19:36 ` Jeff Moyer
2011-02-21 21:14 ` NeilBrown
2011-03-03 14:31 ` Christoph Hellwig
2011-03-04 0:16 ` NeilBrown
2011-03-04 17:25 ` Andrew Patterson
2011-03-06 6:47 ` NeilBrown
2011-03-07 4:22 ` Andrew Patterson
2011-03-07 16:46 ` [dm-devel] " James Bottomley
2011-03-07 22:44 ` NeilBrown
2011-03-07 22:56 ` James Bottomley
2011-03-08 0:04 ` NeilBrown
2011-03-16 20:30 ` Jeff Moyer
2011-03-17 1:28 ` NeilBrown
2011-03-17 17:33 ` Jeff Moyer
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=20110223210100.6d8b95f7@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=krzysztof.wojcik@intel.com \
--cc=linux-raid@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).