Re: kernel panic: MAC Initialization failed. (3)

2019-03-11 Thread Tetsuo Handa
F.Y.I. Nothing is wrong with that commit. That commit merely allows enabling TOMOYO and one of SELinux/Smack/AppArmor at the same time for syzbot's kernel command line options. This problem will be handled by a patch at https://lore.kernel.org/linux-security-module/1551362770-8655-1-git-send-emai

Re: kernel panic: MAC Initialization failed. (3)

2019-03-11 Thread syzbot
syzbot has bisected this bug to: commit 89a9684ea158dd7eef1728be9f0aed9a7d41cf19 Author: Kees Cook Date: Tue Feb 12 18:23:18 2019 + LSM: Ignore "security=" when "lsm=" is specified bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1157272320 start commit: 89a9684e LS

Re: kernel panic: MAC Initialization failed.

2019-02-28 Thread Tetsuo Handa
On 2019/02/28 19:58, Tetsuo Handa wrote: > But the problem is that since syzbot is automated, there is no chance to > edit the content of security/tomoyo/policy/ directory when building the > kernels. Thinking again, I realized that it would be possible to automatically generate the content of sec

Re: kernel panic: MAC Initialization failed.

2019-02-28 Thread Tetsuo Handa
On 2019/02/28 19:23, Dmitry Vyukov wrote: > On Thu, Feb 28, 2019 at 11:20 AM Tetsuo Handa > wrote: >> >> On 2019/02/28 15:51, Dmitry Vyukov wrote: >>> On Wed, Feb 27, 2019 at 11:37 PM Tetsuo Handa Thank you. The LSM stacking seems to be working as expected. But this one should not b

Re: kernel panic: MAC Initialization failed.

2019-02-28 Thread Dmitry Vyukov
On Thu, Feb 28, 2019 at 11:20 AM Tetsuo Handa wrote: > > On 2019/02/28 15:51, Dmitry Vyukov wrote: > > On Wed, Feb 27, 2019 at 11:37 PM Tetsuo Handa > >> > >> Thank you. The LSM stacking seems to be working as expected. > >> But this one should not be considered as a bug. > >> > >> If something we

Re: kernel panic: MAC Initialization failed.

2019-02-28 Thread Tetsuo Handa
On 2019/02/28 15:51, Dmitry Vyukov wrote: > On Wed, Feb 27, 2019 at 11:37 PM Tetsuo Handa >> >> Thank you. The LSM stacking seems to be working as expected. >> But this one should not be considered as a bug. >> >> If something went wrong before loading access control rules, >> it is pointless to co

Re: kernel panic: MAC Initialization failed. (2)

2019-02-28 Thread Dmitry Vyukov
On Thu, Feb 28, 2019 at 11:11 AM Tetsuo Handa wrote: > > On 2019/02/28 15:42, syzbot wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:7b827ff9af88 Add linux-next specific files for 20190227 > > git tree: linux-next > > console output: https://syzkaller.a

Re: kernel panic: MAC Initialization failed. (2)

2019-02-28 Thread Tetsuo Handa
On 2019/02/28 15:42, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:    7b827ff9af88 Add linux-next specific files for 20190227 > git tree:   linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=10f71894c0 > kernel config:  https://syzkal

Re: kernel panic: MAC Initialization failed.

2019-02-27 Thread Dmitry Vyukov
On Wed, Feb 27, 2019 at 11:37 PM Tetsuo Handa wrote: > > On 2019/02/28 2:02, syzbot wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:7b827ff9af88 Add linux-next specific files for 20190227 > > git tree: linux-next > > console output: https://syzkaller.ap

Re: kernel panic: MAC Initialization failed.

2019-02-27 Thread Tetsuo Handa
On 2019/02/28 2:02, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:7b827ff9af88 Add linux-next specific files for 20190227 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=15336f14c0 > kernel config: https://syzkall