From: Sven Eckelmann <sven@narfation.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzkaller <syzkaller@googlegroups.com>,
syzbot <syzbot+a229d8d995b74f8c4b6c@syzkaller.appspotmail.com>,
a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
"David Miller" <davem@davemloft.net>,
"Jakub Kicinski" <jakub.kicinski@netronome.com>,
"Jamal Hadi Salim" <jhs@mojatatu.com>,
"Jiří Pírko" <jiri@resnulli.us>,
LKML <linux-kernel@vger.kernel.org>,
mareklindner@neomailbox.ch, netdev <netdev@vger.kernel.org>,
sw@simonwunderlich.de,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
vinicius.gomes@intel.com, wang.yi59@zte.com.cn,
"Cong Wang" <xiyou.wangcong@gmail.com>
Subject: Re: WARNING in mark_lock (3)
Date: Thu, 28 Nov 2019 09:46:49 +0100 [thread overview]
Message-ID: <1809369.KjlzdqruN6@sven-edge> (raw)
In-Reply-To: <CACT4Y+YwNGWCXBazm+7GHpSw-gXsxmA8NA-o7O7Mpj3d-dhGYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On Thursday, 28 November 2019 09:40:32 CET Dmitry Vyukov wrote:
> On Thu, Nov 28, 2019 at 8:25 AM Sven Eckelmann <sven@narfation.org> wrote:
> >
> > 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").
>
> +syzkaller mailing list for syzbot discussion
>
> Hi Sven,
>
> There is no such functionality at the moment.
> What exactly do you mean? Somehow telling it interactively? Or
> hardcode some set of crashes for linux? I don't see how any of these
> options can really work...
I was thinking more about rerunning the same bisect but tell it to assume
"crashed: general protection fault in batadv_iv_ogm_queue_add" as OK instead
of assuming that it is a crashed like the previous "crashed: WARNING in
mark_lock". Just to get a non-bogus bisect result. Or try to rerun the
bisect between 40e220b4218b and 89d57dddd7d319ded00415790a0bb3c954b7e386
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 8:46 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
2019-11-28 8:40 ` Dmitry Vyukov
2019-11-28 8:46 ` Sven Eckelmann [this message]
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=1809369.KjlzdqruN6@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=dvyukov@google.com \
--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=syzkaller@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