From: Eryu Guan <guaneryu@gmail.com>
To: gregkh@linuxfoundation.org
Cc: tytso@mit.edu, stable@vger.kernel.org, tmhikaru@gmail.com
Subject: Re: FAILED: patch "[PATCH] ext4: iterate over buffer heads correctly in" failed to apply to 4.5-stable tree
Date: Sat, 21 May 2016 19:15:33 +0800 [thread overview]
Message-ID: <20160521111533.GE10350@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1460249484173221@kroah.com>
Hi greg,
On Sat, Apr 09, 2016 at 05:51:24PM -0700, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 4.5-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
4.5 kernel has this patch already, so this failure is expected.
But 4.4 stable needs it as well, and the patch should be applied
cleanly. Can you please consider adding commit 6ffe77bad545 ("ext4:
iterate over buffer heads correctly in move_extent_per_page()") to 4.4
stable tree?
Thanks!
Eryu
>
> thanks,
>
> greg k-h
>
> ------------------ original commit in Linus's tree ------------------
>
> From 87f9a031af48defee9f34c6aaf06d6f1988c244d Mon Sep 17 00:00:00 2001
> From: Eryu Guan <guaneryu@gmail.com>
> Date: Sun, 21 Feb 2016 18:38:44 -0500
> Subject: [PATCH] ext4: iterate over buffer heads correctly in
> move_extent_per_page()
>
> In commit bcff24887d00 ("ext4: don't read blocks from disk after extents
> being swapped") bh is not updated correctly in the for loop and wrong
> data has been written to disk. generic/324 catches this on sub-page
> block size ext4.
>
> Fixes: bcff24887d00 ("ext4: don't read blocks from disk after extentsbeing swapped")
> Signed-off-by: Eryu Guan <guaneryu@gmail.com>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Cc: stable@vger.kernel.org
>
> diff --git a/fs/ext4/move_extent.c b/fs/ext4/move_extent.c
> index e032a0423e35..4098acc701c3 100644
> --- a/fs/ext4/move_extent.c
> +++ b/fs/ext4/move_extent.c
> @@ -390,6 +390,7 @@ data_copy:
> *err = ext4_get_block(orig_inode, orig_blk_offset + i, bh, 0);
> if (*err < 0)
> break;
> + bh = bh->b_this_page;
> }
> if (!*err)
> *err = block_commit_write(pagep[0], from, from + replaced_size);
>
next prev parent reply other threads:[~2016-05-21 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 0:51 FAILED: patch "[PATCH] ext4: iterate over buffer heads correctly in" failed to apply to 4.5-stable tree gregkh
2016-05-21 11:15 ` Eryu Guan [this message]
2016-05-21 18:14 ` Greg KH
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=20160521111533.GE10350@eguan.usersys.redhat.com \
--to=guaneryu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=tmhikaru@gmail.com \
--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