From: Andy Whitcroft <apw@canonical.com>
To: Hugh Dickins <hughd@google.com>
Cc: Allison Henderson <achender@linux.vnet.ibm.com>,
Yongqiang Yang <xiaoqiangnk@gmail.com>, Ted Ts'o <tytso@mit.edu>,
Curt Wohlgemuth <curtw@google.com>,
Surbhi Palande <csurbhi@gmail.com>, Rafael Wysocki <rjw@sisk.pl>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Bug with "fix partial page writes" [3.2-rc regression]
Date: Fri, 9 Dec 2011 13:33:44 +0000 [thread overview]
Message-ID: <20111209133343.GA434@shadowen.org> (raw)
In-Reply-To: <20111208181235.GE2686@shadowen.org>
On Thu, Dec 08, 2011 at 06:12:35PM +0000, Andy Whitcroft wrote:
> On Thu, Dec 08, 2011 at 09:39:55AM -0800, Hugh Dickins wrote:
>
> [...]
> > > [PATCH 1/2] ext4: let mpage_submit_io works well when blocksize < pagesize
> > > [PATCH 2/2] ext4: let ext4_discard_partial_buffers handle pages without
> > >
> > > [PATCH 1/2] ext4: remove a wrong BUG_ON in ext4_ext_convert_to_initialized
> > > [PATCH 2/2] ext4: let ext4_bio_write_page handle EOF correctly
> [...]
> > Only once, before the fixes, did I ever see an unexplained EINVAL
> > (from cp), like Andy reports: I'm very hopeful his case is fixed too.
>
> Yes I have reverted my fix and applied all four of these patches (above).
> I have just completed a 100 iteration run of my test case without failure.
> This would typically fail in the first iteration 90% of the time and
> never survived more than two iterations.
>
> I am comfortable saying they resolve my issue.
Are we likely to see these fixes in a 3.2-rcN or will they be going to
stable?
-apw
next prev parent reply other threads:[~2011-12-09 13:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 22:59 Bug with "fix partial page writes" Curt Wohlgemuth
2011-11-20 20:59 ` Hugh Dickins
2011-11-21 1:59 ` Yongqiang Yang
2011-11-21 1:59 ` Yongqiang Yang
2011-11-21 17:38 ` Allison Henderson
[not found] ` <CAMBkX3cfQ+XS7M5jvXmj8_rBOJ_Afy+YXL7Roj+fswLqBA7i1Q@mail.gmail.com>
2011-11-21 21:26 ` Fwd: " Surbhi Palande
2011-11-22 15:57 ` Allison Henderson
2011-11-22 1:44 ` Yongqiang Yang
2011-11-21 16:56 ` Ted Ts'o
2011-11-21 22:04 ` Hugh Dickins
2011-12-05 23:38 ` Bug with "fix partial page writes" [3.2-rc regression] Hugh Dickins
2011-12-06 1:40 ` Allison Henderson
2011-12-06 3:08 ` Yongqiang Yang
2011-12-06 3:08 ` Yongqiang Yang
2011-12-06 3:20 ` Yongqiang Yang
2011-12-06 3:20 ` Yongqiang Yang
2011-12-06 3:33 ` Tao Ma
2011-12-06 3:44 ` Yongqiang Yang
2011-12-06 3:44 ` Yongqiang Yang
2011-12-06 4:05 ` Allison Henderson
2011-12-06 7:57 ` Yongqiang Yang
2011-12-06 8:55 ` Hugh Dickins
2011-12-06 9:32 ` Yongqiang Yang
2011-12-06 9:32 ` Yongqiang Yang
2011-12-06 22:31 ` Hugh Dickins
2011-12-06 21:15 ` Allison Henderson
2011-12-06 22:47 ` Hugh Dickins
2011-12-07 8:28 ` Yongqiang Yang
2011-12-07 17:04 ` Allison Henderson
2011-12-08 5:10 ` Allison Henderson
2011-12-08 17:39 ` Hugh Dickins
2011-12-08 18:12 ` Andy Whitcroft
2011-12-09 13:33 ` Andy Whitcroft [this message]
2011-12-09 13:44 ` Yongqiang Yang
2011-12-09 16:37 ` Allison Henderson
2011-12-14 4:12 ` Ted Ts'o
2011-12-14 18:07 ` Hugh Dickins
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=20111209133343.GA434@shadowen.org \
--to=apw@canonical.com \
--cc=achender@linux.vnet.ibm.com \
--cc=csurbhi@gmail.com \
--cc=curtw@google.com \
--cc=hughd@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tytso@mit.edu \
--cc=xiaoqiangnk@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.