From: Greg KH <greg@kroah.com>
To: Daniel Rosenberg <drosen@google.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 0/2] A couple recent ext4 CVE fixes
Date: Thu, 11 Oct 2018 11:19:15 +0200 [thread overview]
Message-ID: <20181011091915.GC13455@kroah.com> (raw)
In-Reply-To: <20181006005554.166757-1-drosen@google.com>
On Fri, Oct 05, 2018 at 05:55:52PM -0700, Daniel Rosenberg wrote:
> A couple ext4-related CVE fixes were released to other kernels in
> linux-stable, but didn't cleanly apply to 4.9.y. These are adjusted
> cherry-picks of Ben Hutching's 3.16.y backports.
Now applied, thanks.
greg k-h
next prev parent reply other threads:[~2018-10-11 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 0:55 [PATCH 0/2] A couple recent ext4 CVE fixes Daniel Rosenberg
2018-10-06 0:55 ` [PATCH 1/2] ext4: add corruption check in ext4_xattr_set_entry() Daniel Rosenberg
2018-10-06 0:55 ` [PATCH 2/2] ext4: always verify the magic number in xattr blocks Daniel Rosenberg
2018-10-11 9:19 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-06 0:51 [PATCH 0/2] A couple recent ext4 CVE fixes Daniel Rosenberg
2018-10-11 9:19 ` 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=20181011091915.GC13455@kroah.com \
--to=greg@kroah.com \
--cc=drosen@google.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).