From: James Morris <jmorris@namei.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-security-module@vger.kernel.org,
Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+29569ed06425fcf67a95@syzkaller.appspotmail.com>,
syzbot <syzbot+e1b8084e532b6ee7afab@syzkaller.appspotmail.com>
Subject: Re: [PATCH] tomoyo: Add a kernel config option for fuzzing testing.
Date: Wed, 13 Mar 2019 05:21:52 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1903130519440.27366@namei.org> (raw)
In-Reply-To: <1551362770-8655-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp>
On Thu, 28 Feb 2019, Tetsuo Handa wrote:
> syzbot is reporting kernel panic triggered by memory allocation fault
> injection before loading TOMOYO's policy [1]. To make the fuzzing tests
> useful, we need to assign a profile other than "disabled" (no-op) mode.
> Therefore, let's allow syzbot to load TOMOYO's built-in policy for
> "learning" mode using a kernel config option. This option must not be
> enabled for kernels built for production system, for this option also
> disables domain/program checks when modifying policy configuration via
> /sys/kernel/security/tomoyo/ interface.
I don't understand the logic here. If the cause of this is no policy
loaded combined with running out of memory, shouldn't the no-policy issue
be dealt with earlier?
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-03-12 18:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 14:06 [PATCH] tomoyo: Add a kernel config option for fuzzing testing Tetsuo Handa
2019-03-04 13:35 ` Tetsuo Handa
2019-03-04 14:34 ` Stephen Smalley
2019-03-04 23:59 ` Tetsuo Handa
2019-03-05 3:32 ` James Morris
2019-03-11 13:18 ` Tetsuo Handa
2019-03-12 17:19 ` James Morris
2019-03-12 21:15 ` Tetsuo Handa
2019-03-12 21:19 ` James Morris
2019-03-12 21:56 ` Edwin Zimmerman
2019-03-13 20:00 ` James Morris
2019-03-12 18:21 ` James Morris [this message]
2019-03-12 20:56 ` Tetsuo Handa
2019-03-12 21:24 ` James Morris
2019-03-13 10:29 ` Tetsuo Handa
2019-03-13 13:17 ` Paul Moore
2019-03-25 21:09 ` Tetsuo Handa
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.1903130519440.27366@namei.org \
--to=jmorris@namei.org \
--cc=dvyukov@google.com \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=syzbot+29569ed06425fcf67a95@syzkaller.appspotmail.com \
--cc=syzbot+e1b8084e532b6ee7afab@syzkaller.appspotmail.com \
/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.