aboutsummaryrefslogtreecommitdiffstats
path: root/security/tomoyo/network.c
diff options
context:
space:
mode:
authorTetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>2019-04-12 20:04:54 +0900
committerJames Morris <jamorris@linux.microsoft.com>2019-05-10 14:58:11 -0700
commite80b18599a39a625bc8b2e39ba3004a62f78805a (patch)
treecbac414dedf2b92c218906bbdcda5b3497bb5cac /security/tomoyo/network.c
parentMerge tag 'docs-5.2a' of git://git.lwn.net/linux (diff)
downloadlinux-dev-e80b18599a39a625bc8b2e39ba3004a62f78805a.tar.xz
linux-dev-e80b18599a39a625bc8b2e39ba3004a62f78805a.zip
tomoyo: Add a kernel config option for fuzzing testing.
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. [1] https://syzkaller.appspot.com/bug?extid=29569ed06425fcf67a95 Reported-by: syzbot <syzbot+e1b8084e532b6ee7afab@syzkaller.appspotmail.com> Reported-by: syzbot <syzbot+29569ed06425fcf67a95@syzkaller.appspotmail.com> Reported-by: syzbot <syzbot+2ee3f8974c2e7dc69feb@syzkaller.appspotmail.com> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> Signed-off-by: James Morris <jamorris@linux.microsoft.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions