linux-kernel - Re: INFO: rcu detected stall in sys

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+bURugCpLm5TG37-7voFEeEoXo_Gb=3sy75_RELZotXHw@mail.gmail.com>
Date:   Thu, 9 Jan 2020 09:19:57 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Casey Schaufler <casey@...aufler-ca.com>
Cc:     Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        syzbot <syzbot+de8d933e7d153aa0c1bb@...kaller.appspotmail.com>,
        kasan-dev <kasan-dev@...glegroups.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: INFO: rcu detected stall in sys_kill

On Wed, Jan 8, 2020 at 6:19 PM Casey Schaufler <casey@...aufler-ca.com> wrote:
>
> On 1/8/2020 2:25 AM, Tetsuo Handa wrote:
> > On 2020/01/08 15:20, Dmitry Vyukov wrote:
> >> I temporarily re-enabled smack instance and it produced another 50
> >> stalls all over the kernel, and now keeps spewing a dozen every hour.
>
> Do I have to be using clang to test this? I'm setting up to work on this,
> and don't want to waste time using my current tool chain if the problem
> is clang specific.

Humm, interesting. Initially I was going to say that most likely it's
not clang-related. Bug smack instance is actually the only one that
uses clang as well (except for KMSAN of course). So maybe it's indeed
clang-related rather than smack-related. Let me try to build a kernel
with clang.

> > Since we can get stall reports rather easily, can we try modifying
> > kernel command line (e.g. lsm=smack) and/or kernel config (e.g. no kasan) ?
> >
> >> I've mailed 3 new samples, you can see them here:
> >> https://syzkaller.appspot.com/bug?extid=de8d933e7d153aa0c1bb
> >>
> >> The config is provided, command line args are here:
> >> https://github.com/google/syzkaller/blob/master/dashboard/config/upstream-smack.cmdline
> >> Some non-default sysctls that syzbot sets are here:
> >> https://github.com/google/syzkaller/blob/master/dashboard/config/upstream.sysctl
> >> Image can be downloaded from here:
> >> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#crash-does-not-reproduce
> >> syzbot uses GCE VMs with 2 CPUs and 7.5GB memory, but this does not
> >> look to be virtualization-related (?) so probably should reproduce in
> >> qemu too.
> > Is it possible to add instance for linux-next.git that uses these configs?
> > If yes, we could try adding some debug printk() under CONFIG_DEBUG_AID_FOR_SYZBOT=y .