WARNING: locking bug in tomoyo_supervisor
penguin-kernel at i-love.sakura.ne.jp
Fri Apr 17 04:37:31 UTC 2020
On 2020/04/17 7:05, syzbot wrote:
> syzbot found the following crash on:
> HEAD commit: 4f8a3cc1 Merge tag 'x86-urgent-2020-04-12' of git://git.ke..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1599027de00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3bfbde87e8e65624
> dashboard link: https://syzkaller.appspot.com/bug?extid=1c36440b364ea3774701
> compiler: clang version 10.0.0 (https://github.com/llvm/llvm-project/ c2443155a0fb245c8f17f2c1c72b6ea391e86e81)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=150733cde00000
This seems to be a misattributed report explained at https://email@example.com .
Petr and Sergey, how is the progress of making printk() asynchronous? When can we expect that work to be merged?
If it is delaying, can we implement storing these metadata into the per-CPU buffers?
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10aacf5de00000
bisection log says this will be a duplicate of
#syz dup: WARNING: locking bug in inet_autobind
. This misattribution by chance served as a reminder for "locking bug in inet_autobind" bug. ;-)
According to https://syzkaller.appspot.com/bug?id=a7d678fba80c34b5770cc1b5638b8a2709ae9f3f ,
this bug is happening on "2020/04/01 19:28", "2020/04/09 06:24" and "2020/04/10 20:48"
which are after the opening of the merge window for 5.7-rc1. Reproducer suggests that
pppl2tp and inet6_udp are relevant.
More information about the Linux-security-module-archive