All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+fdce8f2a8903f3ba0e6b@syzkaller.appspotmail.com>,
	arvid.brodin@alten.se, Jens Axboe <axboe@fb.com>,
	Jens Axboe <axboe@kernel.dk>, David Miller <davem@davemloft.net>,
	Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org, linux-can@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Ming Lei <ming.lei@redhat.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	netdev <netdev@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING in hsr_forward_skb
Date: Wed, 13 Mar 2019 19:22:54 +0100	[thread overview]
Message-ID: <cc1224f9-8fdc-ed08-3004-ae528dbeadb8@hartkopp.net> (raw)
In-Reply-To: <CACT4Y+ayyFe6oek8MdnUd1LsB_+1kpJatBLnmF_jCttQPyCK0g@mail.gmail.com>

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


  reply	other threads:[~2019-03-13 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 10:31 WARNING in hsr_forward_skb syzbot
2019-03-12  8:57 ` syzbot
2019-03-12 12:01   ` Oliver Hartkopp
2019-03-12 16:09     ` Dmitry Vyukov
2019-03-12 16:21       ` Dmitry Vyukov
2019-03-13 18:22         ` Oliver Hartkopp [this message]
2021-05-09 15:16 ` [syzbot] " syzbot
2021-05-10  6:09   ` Dmitry Vyukov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc1224f9-8fdc-ed08-3004-ae528dbeadb8@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=arvid.brodin@alten.se \
    --cc=axboe@fb.com \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+fdce8f2a8903f3ba0e6b@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.