stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Török Edwin" <edwin@etorok.net>
Cc: stable@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
	linux-ext4@vger.kernel.org
Subject: Re: Fwd: [STABLE CHERRYPICK] ext4: avoid modifying checksum fields directly during checksum verification
Date: Thu, 8 Sep 2016 10:56:15 +0200	[thread overview]
Message-ID: <20160908085615.GA21050@kroah.com> (raw)
In-Reply-To: <40811621-e317-fecc-8052-56b88fd5ce35@etorok.net>

On Thu, Sep 08, 2016 at 10:21:34AM +0300, T�r�k Edwin wrote:
> Hi,
> 
> Not sure if this was sent to the right place: stable@kernel.org
> doesn't seem to exist, I can't find this message in the ML archives,
> or the 4.7.3 changelog.  Could you please include this in 4.7.4, I've
> been waiting for this patch to get included ever since 4.7.1...

Yeah, I never saw it.

Will add it to the queue, it's long, might take a release or two to make
it...

Were there any objections from the ext4 maintainers in taking the patch
below?

thanks,

greg k-h

> -------- Forwarded Message --------
> Subject: [STABLE CHERRYPICK] ext4: avoid modifying checksum fields directly during checksum verification
> Date: Mon, 5 Sep 2016 22:29:55 -0400
> From: Theodore Ts'o <tytso@mit.edu>
> To: stable@kernel.org
> CC: linux-ext4@vger.kernel.org, T�r�k Edwin <edwin@etorok.net>
> 
> Hi, please cherry pick the following commit into the stable kernels.
> The commit landed in 4.8-rc1.  It wasn't marked with a cc:
> stable@kernel.org, but it should be backported since it affecting a
> number of users who are trying to use ext4's metadata checksum
> feature.
> 
> Thanks!!
> 
> commit b47820edd1634dc1208f9212b7ecfb4230610a23
> Author: Daeho Jeong <daeho.jeong@samsung.com>
> Date:   Sun Jul 3 17:51:39 2016 -0400
> 
>     ext4: avoid modifying checksum fields directly during checksum verification
>     
>     We temporally change checksum fields in buffers of some types of
>     metadata into '0' for verifying the checksum values. By doing this
>     without locking the buffer, some metadata's checksums, which are
>     being committed or written back to the storage, could be damaged.
>     In our test, several metadata blocks were found with damaged metadata
>     checksum value during recovery process. When we only verify the
>     checksum value, we have to avoid modifying checksum fields directly.
>     
>     Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
>     Signed-off-by: Youngjin Gil <youngjin.gil@samsung.com>
>     Signed-off-by: Theodore Ts'o <tytso@mit.edu>
>     Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> 
> 						- Ted
> 						
> 
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-09-08  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160906022955.qopdwuznvtqlwofq@thunk.org>
2016-09-08  7:21 ` Fwd: [STABLE CHERRYPICK] ext4: avoid modifying checksum fields directly during checksum verification Török Edwin
2016-09-08  8:56   ` Greg KH [this message]
2016-09-08 15:27     ` Darrick J. Wong
2016-09-09 14:11     ` 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=20160908085615.GA21050@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=edwin@etorok.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=stable@vger.kernel.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).