From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Hartkopp Subject: Re: WARNING in hsr_forward_skb Date: Wed, 13 Mar 2019 19:22:54 +0100 Message-ID: References: <0000000000004cfa120583e1dfc3@google.com> <7dd5ffca-803d-9d5e-7fa4-f9eed2249d26@hartkopp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org To: Dmitry Vyukov Cc: syzbot , arvid.brodin@alten.se, Jens Axboe , Jens Axboe , David Miller , Christoph Hellwig , linux-block@vger.kernel.org, linux-can@vger.kernel.org, LKML , Ming Lei , Marc Kleine-Budde , netdev , syzkaller-bugs List-Id: linux-can.vger.kernel.org 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