From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <Alexander.Levin@microsoft.com>
Cc: stable <stable@vger.kernel.org>, linux-btrfs@vger.kernel.org
Subject: Security fixes for 4.4 - btrfs
Date: Fri, 11 Jan 2019 14:49:11 +0000 [thread overview]
Message-ID: <1547218151.3229.73.camel@codethink.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
I've backported fixes for several security issues involving filesystem
validation in btrfs. 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).
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
[-- Attachment #2: security-4.4-btrfs.mbox --]
[-- Type: application/mbox, Size: 146854 bytes --]
next reply other threads:[~2019-01-11 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 14:49 Ben Hutchings [this message]
2019-01-14 13:50 ` Security fixes for 4.4 - btrfs Greg Kroah-Hartman
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=1547218151.3229.73.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-btrfs@vger.kernel.org \
--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 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.