From: Dave Jones <davej@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, Zheng Liu <gnehzuil.liu@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 4/4] ext4: Fix lost truncate due to race with writeback
Date: Wed, 28 Aug 2013 19:01:47 -0400 [thread overview]
Message-ID: <20130828230147.GA4573@redhat.com> (raw)
In-Reply-To: <20130828225504.GL27079@thunk.org>
On Wed, Aug 28, 2013 at 06:55:04PM -0400, Theodore Ts'o wrote:
> On Mon, Aug 26, 2013 at 03:01:48PM -0400, Dave Jones wrote:
> >
> > Is this queued for 3.11 ? 1k blocksize fs's are still broken in rc7.
>
> These patches fixed races that have been around for a while; it's not
> a regression. Given that they are fairly involved, I was nervous
> sending them to Linus for 3.11, given the late date.
That's odd, because I can't reproduce the problem I'm seeing on 3.10
> They are queued for the next merge window, and I'll mark them cc:
> stable@vger.kernel.org.
Fair enough.
Dave
prev parent reply other threads:[~2013-08-28 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 13:52 [PATCH 0/4 v2] ext4: Fix races between writeback and truncate Jan Kara
2013-08-05 13:52 ` [PATCH 1/4] ext4: Move test whether extent to map can be extended to one place Jan Kara
2013-08-17 13:59 ` Theodore Ts'o
2013-08-05 13:52 ` [PATCH 2/4] ext4: Fix ext4_writepages() in presence of truncate Jan Kara
2013-08-17 14:08 ` Theodore Ts'o
2013-08-05 13:52 ` [PATCH 3/4] ext4: Simplify truncation code in ext4_setattr() Jan Kara
2013-08-17 14:08 ` Theodore Ts'o
2013-08-05 13:52 ` [PATCH 4/4] ext4: Fix lost truncate due to race with writeback Jan Kara
2013-08-17 14:12 ` Theodore Ts'o
2013-08-26 19:01 ` Dave Jones
2013-08-28 22:55 ` Theodore Ts'o
2013-08-28 23:01 ` Dave Jones [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=20130828230147.GA4573@redhat.com \
--to=davej@redhat.com \
--cc=gnehzuil.liu@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).