From: Sven Eckelmann <sven@narfation.org>
To: syzbot <syzbot+a229d8d995b74f8c4b6c@syzkaller.appspotmail.com>
Cc: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
davem@davemloft.net, jakub.kicinski@netronome.com,
jhs@mojatatu.com, jiri@resnulli.us, linux-kernel@vger.kernel.org,
mareklindner@neomailbox.ch, netdev@vger.kernel.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
vinicius.gomes@intel.com, wang.yi59@zte.com.cn,
xiyou.wangcong@gmail.com
Subject: Re: WARNING in mark_lock (3)
Date: Thu, 28 Nov 2019 08:25:34 +0100 [thread overview]
Message-ID: <2825703.dkhYCMB3mh@sven-edge> (raw)
In-Reply-To: <0000000000009aa32205985e78b6@google.com>
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
On Thursday, 28 November 2019 03:00:01 CET syzbot wrote:
[...]
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132ee536e00000
> start commit: 89d57ddd Merge tag 'media/v5.5-1' of git://git.kernel.org/..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=10aee536e00000
Can the syzbot infrastructure be told to ignore this crash in the bisect run?
Because this should be an unrelated crash which is (hopefully) fixed in
40e220b4218b ("batman-adv: Avoid free/alloc race when handling OGM buffer").
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-28 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 9:05 WARNING in mark_lock (3) syzbot
2019-11-27 19:30 ` syzbot
2019-11-28 2:00 ` syzbot
2019-11-28 7:25 ` Sven Eckelmann [this message]
2019-11-28 8:40 ` Dmitry Vyukov
2019-11-28 8:46 ` Sven Eckelmann
2019-11-28 8:54 ` Dmitry Vyukov
2019-11-28 9:03 ` Sven Eckelmann
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=2825703.dkhYCMB3mh@sven-edge \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
--cc=syzbot+a229d8d995b74f8c4b6c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vinicius.gomes@intel.com \
--cc=wang.yi59@zte.com.cn \
--cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).