From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org,
Shankara Pailoor <shankarapailoor@gmail.com>,
Dave Kleikamp <dave.kleikamp@oracle.com>
Subject: Re: Please apply commit 92d34134193e ("fs: Fix inconsistency ..." to stable releases
Date: Tue, 7 Aug 2018 18:41:36 +0200 [thread overview]
Message-ID: <20180807164136.GA7441@kroah.com> (raw)
In-Reply-To: <20180807162721.GA29471@roeck-us.net>
On Tue, Aug 07, 2018 at 09:27:21AM -0700, Guenter Roeck wrote:
> Hi Greg,
>
> commit 92d34134193e ("jfs: Fix inconsistency between memory allocation and
> ea_buf->max_size") fixes CVE-2018-12233. As far as I can see, the commit is
> not in any stable releases. It applies to all stable releases at least as
> far back as v4.4.y (and it builds unless I really messed up).
>
> Copying author and committer in case there are any concerns. Otherwise,
> please apply to stable releases.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2018-08-07 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 16:27 Please apply commit 92d34134193e ("fs: Fix inconsistency ..." to stable releases Guenter Roeck
2018-08-07 16:41 ` Greg Kroah-Hartman [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=20180807164136.GA7441@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dave.kleikamp@oracle.com \
--cc=linux@roeck-us.net \
--cc=shankarapailoor@gmail.com \
--cc=stable@vger.kernel.org \
/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).