[PATCH] tomoyo: Add a kernel config option for fuzzing testing.
sds at tycho.nsa.gov
Mon Mar 4 14:34:21 UTC 2019
On 3/4/19 8:35 AM, Tetsuo Handa wrote:
> James, please include this patch for 5.1-rc1, for failing to include
> this patch will prevent various trees (SELinux/Smack/AppArmor) from
> proper testing due to this problem because syzbot is enabling both
> TOMOYO and one of SELinux/Smack/AppArmor via lsm= boot parameter.
> By including this patch and building kernels with this config option
> enabled, syzbot will be able to continue proper testing.
Could you clarify the status of upstream TOMOYO? Is its MAINTAINERS
entry still accurate? Is it still actively maintained? Its existing
documentation (in-tree and the tomoyo.osdn.jp site) seem to suggest that
using the pre-LSM version and/or AKARI are preferred to using the
upstream version. Is that still true, and do you envision it changing?
> On 2019/02/28 23:06, Tetsuo Handa wrote:
>> syzbot is reporting kernel panic triggered by memory allocation fault
>> injection before loading TOMOYO's policy . 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.
>>  https://syzkaller.appspot.com/bug?extid=29569ed06425fcf67a95
>> Reported-by: syzbot <syzbot+e1b8084e532b6ee7afab at syzkaller.appspotmail.com>
>> Reported-by: syzbot <syzbot+29569ed06425fcf67a95 at syzkaller.appspotmail.com>
>> Signed-off-by: Tetsuo Handa <penguin-kernel at I-love.SAKURA.ne.jp>
>> security/tomoyo/Kconfig | 10 ++++++++++
>> security/tomoyo/common.c | 13 ++++++++++++-
>> 2 files changed, 22 insertions(+), 1 deletion(-)
More information about the Linux-security-module-archive