From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] security subsystem: Tomoyo updates for v5.2
Date: Sat, 11 May 2019 08:09:22 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1905110801350.9392@namei.org> (raw)
Please pull.
These patches include fixes to enable fuzz testing, and a fix for
calculating whether a filesystem is user-modifiable.
The following changes since commit 1fb3b526df3bd7647e7854915ae6b22299408baf:
Merge tag 'docs-5.2a' of git://git.lwn.net/linux (2019-05-10 13:24:53 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-tomoyo2
for you to fetch changes up to 4ad98ac46490d5f8441025930070eaf028cfd0f2:
tomoyo: Don't emit WARNING: string while fuzzing testing. (2019-05-10 14:58:35 -0700)
----------------------------------------------------------------
Tetsuo Handa (4):
tomoyo: Add a kernel config option for fuzzing testing.
tomoyo: Check address length before reading address family
tomoyo: Change pathname calculation for read-only filesystems.
tomoyo: Don't emit WARNING: string while fuzzing testing.
security/tomoyo/Kconfig | 10 ++++++++++
security/tomoyo/common.c | 13 ++++++++++++-
security/tomoyo/network.c | 4 ++++
security/tomoyo/realpath.c | 3 ++-
security/tomoyo/util.c | 2 ++
5 files changed, 30 insertions(+), 2 deletions(-)
next reply other threads:[~2019-05-10 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 22:09 James Morris [this message]
2019-05-11 14:38 ` Linus Torvalds
2019-05-11 18:13 ` Paul Moore
2019-05-11 22:08 ` Casey Schaufler
2019-05-12 15:33 ` Paul Moore
2019-05-12 19:17 ` Linus Torvalds
2019-05-13 18:03 ` James Morris
2019-05-13 17:53 ` James Morris
2019-05-13 18:22 ` James Morris
2019-05-11 15:00 ` pr-tracker-bot
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=alpine.LRH.2.21.1905110801350.9392@namei.org \
--to=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®