From: Greg KH <gregkh@linuxfoundation.org>
To: Chenbo Feng <fengc@google.com>
Cc: stable@vger.kernel.org, kernel-team@android.com,
Theodore Ts'o <tytso@mit.edu>,
stable@kernel.org
Subject: Re: [4.9.y v2] ext4: avoid running out of journal credits when appending to an inline file
Date: Tue, 16 Oct 2018 16:03:55 +0200 [thread overview]
Message-ID: <20181016140355.GF20256@kroah.com> (raw)
In-Reply-To: <20181011185142.104586-2-fengc@google.com>
On Thu, Oct 11, 2018 at 11:51:42AM -0700, Chenbo Feng wrote:
> From: Theodore Ts'o <tytso@mit.edu>
>
> commit 8bc1379b82b8e809eef77a9fedbb75c6c297be19 upstream.
>
> Use a separate journal transaction if it turns out that we need to
> convert an inline file to use an data block. Otherwise we could end
> up failing due to not having journal credits.
>
> This addresses CVE-2018-10883.
>
> https://bugzilla.kernel.org/show_bug.cgi?id=200071
>
> Change-Id: Ifbe92e379f7a25fb252a2584356ccb91f902ea8f
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Cc: stable@kernel.org
> [fengc@google.com: 4.4 and 4.9 backport: adjust context]
> Signed-off-by: Chenbo Feng <fengc@google.com>
> ---
> fs/ext4/ext4.h | 3 ---
> fs/ext4/inline.c | 38 +-------------------------------------
> fs/ext4/xattr.c | 18 ++----------------
> 3 files changed, 3 insertions(+), 56 deletions(-)
This patch still does not apply to the latest 4.9 stable tree, can you
rebase these again? There's been a lot of patches happening in this
area recently, sorry.
greg k-h
next prev parent reply other threads:[~2018-10-16 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 18:51 [4.4.y v2] ext4: avoid running out of journal credits when appending to an inline file Chenbo Feng
2018-10-11 18:51 ` [4.9.y " Chenbo Feng
2018-10-16 14:03 ` Greg KH [this message]
2018-10-16 21:08 ` Chenbo Feng
2018-10-18 17:03 ` [4.4.y " Greg KH
2018-10-18 19:13 ` Chenbo Feng
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=20181016140355.GF20256@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fengc@google.com \
--cc=kernel-team@android.com \
--cc=stable@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 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.