From: Bart Van Assche <bvanassche@acm.org>
To: syzbot <syzbot+bd3bba6ff3fcea7a6ec6@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, hawk@kernel.org,
jakub.kicinski@netronome.com, johannes.berg@intel.com,
johannes@sipsolutions.net, john.fastabend@gmail.com,
kafai@fb.com, linux-kernel@vger.kernel.org, longman@redhat.com,
mingo@kernel.org, netdev@vger.kernel.org,
paulmck@linux.vnet.ibm.com, peterz@infradead.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tj@kernel.org, torvalds@linux-foundation.org,
will.deacon@arm.com, xdp-newbies@vger.kernel.org, yhs@fb.com,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: WARNING in is_bpf_text_address
Date: Fri, 28 Jun 2019 08:17:16 -0700 [thread overview]
Message-ID: <c0e440a1-30aa-a636-fe5c-44f71705857b@acm.org> (raw)
In-Reply-To: <000000000000104b00058c61eda4@google.com>
On 6/28/19 6:05 AM, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit a0b0fd53e1e67639b303b15939b9c653dbe7a8c4
> Author: Bart Van Assche <bvanassche@acm.org>
> Date: Thu Feb 14 23:00:46 2019 +0000
>
> locking/lockdep: Free lock classes that are no longer in use
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=152f6a9da00000
> start commit: abf02e29 Merge tag 'pm-5.2-rc6' of
> git://git.kernel.org/pu..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=172f6a9da00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=132f6a9da00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=28ec3437a5394ee0
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=bd3bba6ff3fcea7a6ec6
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ae828aa00000
>
> Reported-by: syzbot+bd3bba6ff3fcea7a6ec6@syzkaller.appspotmail.com
> Fixes: a0b0fd53e1e6 ("locking/lockdep: Free lock classes that are no
> longer in use")
>
> For information about bisection process see:
> https://goo.gl/tpsmEJ#bisection
Dmitry, this bisection result does not make any sense to me. Can I mark
this bisection result myself as invalid?
Thanks,
Bart.
next prev parent reply other threads:[~2019-06-28 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 12:57 WARNING in is_bpf_text_address syzbot
2019-06-28 13:05 ` syzbot
2019-06-28 15:17 ` Bart Van Assche [this message]
2019-07-01 8:12 ` Dmitry Vyukov
2019-08-11 0:24 ` syzbot
2019-08-15 7:51 ` Will Deacon
2019-08-16 1:39 ` Bart Van Assche
2019-08-16 8:21 ` Will Deacon
[not found] <20190811083658.10748-1-hdanton@sina.com>
2019-08-15 8:52 ` Daniel Borkmann
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=c0e440a1-30aa-a636-fe5c-44f71705857b@acm.org \
--to=bvanassche@acm.org \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=hawk@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=syzbot+bd3bba6ff3fcea7a6ec6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=xdp-newbies@vger.kernel.org \
--cc=yhs@fb.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).