From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <Alexander.Levin@microsoft.com>,
stable <stable@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Security fixes for 4.4 - f2fs
Date: Tue, 22 Jan 2019 14:51:01 +0000 [thread overview]
Message-ID: <1548168661.3229.185.camel@codethink.co.uk> (raw)
In-Reply-To: <20190118081946.GA17484@kroah.com>
On Fri, 2019-01-18 at 09:19 +0100, Greg Kroah-Hartman wrote:
> On Thu, Jan 17, 2019 at 07:28:47PM +0000, Ben Hutchings wrote:
> > I've backported fixes for several security issues involving
> > filesystem
> > validation in f2fs. All of these are already fixed in the later
> > stable
> > branches.
> >
> > I tested with the reproducers where available. I also checked for
> > regressions with xfstests and didn't find any (but many tests fail
> > with
> > or without these changes).
>
> Thanks for all of these, now queued up.
>
> Note, one of these, d4fdf8ba0e58 ("f2fs: fix a panic caused by NULL
> flush_cmd_control"), was already in the 4.4.169 release.
Sorry about that - it took me some time to prepare and test these and I
was starting from a base of 4.4.167.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next prev parent reply other threads:[~2019-01-22 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 19:28 Security fixes for 4.4 - f2fs Ben Hutchings
2019-01-18 8:19 ` Greg Kroah-Hartman
2019-01-22 14:51 ` Ben Hutchings [this message]
2019-01-29 12:41 ` Jiri Slaby
2019-02-05 13:59 ` Ben Hutchings
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=1548168661.3229.185.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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).