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: <cc1224f9-8fdc-ed08-3004-ae528dbeadb8@hartkopp.net>
Date:   Wed, 13 Mar 2019 19:22:54 +0100
From:   Oliver Hartkopp <socketcan@...tkopp.net>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     syzbot <syzbot+fdce8f2a8903f3ba0e6b@...kaller.appspotmail.com>,
        arvid.brodin@...en.se, Jens Axboe <axboe@...com>,
        Jens Axboe <axboe@...nel.dk>,
        David Miller <davem@...emloft.net>,
        Christoph Hellwig <hch@....de>, linux-block@...r.kernel.org,
        linux-can@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        Ming Lei <ming.lei@...hat.com>,
        Marc Kleine-Budde <mkl@...gutronix.de>,
        netdev <netdev@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: WARNING in hsr_forward_skb

Hi Dimitry,

On 3/12/19 5:21 PM, Dmitry Vyukov wrote:

>> You can see how bisection progressed and got to 4.12.0-rc2+ in the
>> bisection log.
>>
>> The commit that it come up with looks unrelated.
>> I've started collecting such cases at:
>> https://github.com/google/syzkaller/issues/1051
>> and added for this case:
>>
>> =====
>> Bisected to wrong commit.
>> Root cause: broken kernel boots, bugs that happen on all tests.
>> Boot is broken for several releases with "WARNING in hsr_forward_skb",
>> this switches to a bug that happens during every test "INFO: trying to
>> register non-static key in can_notifier", which then leads to a
>> completely random commit.
>> =====
> 
> Broken boots did not happen here. "WARNING in hsr_forward_skb" is the
> crash that we pursued, so it started correctly. But then diverged to
> an unrelated "INFO: trying to register non-static key in
> can_notifier".

Thanks for the clarification! I really appreciate your effort with syzbot!

Best,
Oliver

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ