From: Sasha Levin <sashal@kernel.org>
To: Suraj Jitindar Singh <surajjs@amazon.com>
Cc: stable@vger.kernel.org, tytso@mit.edu, stable@kernel.org
Subject: Re: [PATCH 4.14.x 1/3] ext4: fix potential race between online resizing and write operations
Date: Fri, 28 Feb 2020 22:59:04 -0500 [thread overview]
Message-ID: <20200229035904.GI21491@sasha-vm> (raw)
In-Reply-To: <20200229004817.13283-1-surajjs@amazon.com>
On Fri, Feb 28, 2020 at 04:48:15PM -0800, Suraj Jitindar Singh wrote:
>From: Theodore Ts'o <tytso@mit.edu>
>
>commit 1d0c3924a92e69bfa91163bda83c12a994b4d106 upstream.
>
>During an online resize an array of pointers to buffer heads gets
>replaced so it can get enlarged. If there is a racing block
>allocation or deallocation which uses the old array, and the old array
>has gotten reused this can lead to a GPF or some other random kernel
>memory getting modified.
>
>Link: https://bugzilla.kernel.org/show_bug.cgi?id=206443
>Link: https://lore.kernel.org/r/20200221053458.730016-2-tytso@mit.edu
>Reported-by: Suraj Jitindar Singh <surajjs@amazon.com>
>Signed-off-by: Theodore Ts'o <tytso@mit.edu>
>Cc: stable@kernel.org # 4.14.x
I've applied this and the 4.9 and 4.4 series.
Note that patch 2 in all of your serieses didn't apply cleanly for me,
but cherry picking the upstream commit directly worked so I did that.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-29 3:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 8:08 FAILED: patch "[PATCH] ext4: fix potential race between online resizing and write" failed to apply to 4.14-stable tree gregkh
2020-02-29 0:48 ` [PATCH 4.14.x 1/3] ext4: fix potential race between online resizing and write operations Suraj Jitindar Singh
2020-02-29 0:48 ` [PATCH 4.14.x 2/3] ext4: fix potential race between s_group_info online resizing and access Suraj Jitindar Singh
2020-02-29 0:48 ` [PATCH 4.14.x 3/3] ext4: fix potential race between s_flex_groups " Suraj Jitindar Singh
2020-02-29 3:59 ` Sasha Levin [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=20200229035904.GI21491@sasha-vm \
--to=sashal@kernel.org \
--cc=stable@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surajjs@amazon.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