From: Bart Van Assche <bvanassche@acm.org>
To: Will Deacon <will@kernel.org>,
syzbot <syzbot+bd3bba6ff3fcea7a6ec6@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, dvyukov@google.com,
hawk@kernel.org, hdanton@sina.com, 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
Subject: Re: WARNING in is_bpf_text_address
Date: Thu, 15 Aug 2019 18:39:56 -0700 [thread overview]
Message-ID: <456d0da6-3e16-d3fc-ecf6-7abb410bf689@acm.org> (raw)
In-Reply-To: <20190815075142.vuza32plqtiuhixx@willie-the-truck>
On 8/15/19 12:51 AM, Will Deacon wrote:
> Hi Bart,
>
> On Sat, Aug 10, 2019 at 05:24:06PM -0700, syzbot wrote:
>> syzbot has found a reproducer for the following crash on:
>>
>> HEAD commit: 451577f3 Merge tag 'kbuild-fixes-v5.3-3' of git://git.kern..
>> git tree: upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=120850a6600000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=2031e7d221391b8a
>> dashboard link: https://syzkaller.appspot.com/bug?extid=bd3bba6ff3fcea7a6ec6
>> compiler: clang version 9.0.0 (/home/glider/llvm/clang
>> 80fee25776c2fb61e74c1ecb1a523375c2500b69)
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=130ffe4a600000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17137d2c600000
>>
>> The bug was bisected 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
>> final crash: https://syzkaller.appspot.com/x/report.txt?x=172f6a9da00000
>> console output: https://syzkaller.appspot.com/x/log.txt?x=132f6a9da00000
>
> I know you don't think much to these reports, but please could you have a
> look (even if it's just to declare it a false positive)?
Hi Will,
Had you already noticed the following message?
https://lore.kernel.org/bpf/d76d7a63-7854-e92d-30cb-52546d333ffe@iogearbox.net/
From that message: "Hey Bart, don't think it's related in any way to
your commit. I'll allocate some time on working on this issue today,
thanks!"
Bart.
next prev parent reply other threads:[~2019-08-16 1:42 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
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 [this message]
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=456d0da6-3e16-d3fc-ecf6-7abb410bf689@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=hdanton@sina.com \
--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=will@kernel.org \
--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).