linux-kernel - Re: WARNING in port

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: <20190401192413.GQ4102@linux.ibm.com>
Date:   Mon, 1 Apr 2019 12:24:14 -0700
From:   "Paul E. McKenney" <paulmck@...ux.ibm.com>
To:     syzbot <syzbot+e4c8abb920efa77bace9@...kaller.appspotmail.com>
Cc:     alsa-devel-bounces@...a-project.org, alsa-devel@...a-project.org,
        colin.king@...onical.com, linux-kernel@...r.kernel.org,
        mingo@...hat.com, perex@...ex.cz, rostedt@...dmis.org,
        syzkaller-bugs@...glegroups.com, tiwai@...e.com
Subject: Re: WARNING in port_delete

On Mon, Apr 01, 2019 at 12:58:01AM -0700, syzbot wrote:
> syzbot has bisected this bug to:
> 
> commit 63d86a7e85f84b8ac3b2f394570965aedbb03787
> Author: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> Date:   Tue May 1 20:08:46 2018 +0000
> 
>     rcu: Convert rcu_grace_period_init tracepoint to gp_seq
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17f86d2f200000
> start commit:   091a1eaa Merge branch 'akpm'
> git tree:       upstream
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=14046d2f200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=10046d2f200000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=c0af03fe452b65fb
> dashboard link: https://syzkaller.appspot.com/bug?extid=e4c8abb920efa77bace9
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=102e2c91400000
> 
> Reported-by: syzbot+e4c8abb920efa77bace9@...kaller.appspotmail.com
> Fixes: 63d86a7e85f8 ("rcu: Convert rcu_grace_period_init tracepoint
> to gp_seq")

I could easily be suffering from a lack of imagination, but I am not
seeing how this change to RCU's event tracing could cause this result.
Especially given that CONFIG_RCU_TRACE=n in your .config.

What am I missing here?

							Thanx, Paul

> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>