Re: WARNING in is_bpf_text_address

[Will Deacon]

On Thu, Aug 15, 2019 at 06:39:56PM -0700, Bart Van Assche wrote:
> On 8/15/19 12:51 AM, Will Deacon wrote:
> > On Sat, Aug 10, 2019 at 05:24:06PM -0700, syzbot wrote:
> > > The bug was bisected to:
> > > 
> > > commit a0b0fd53e1e67639b303b15939b9c653dbe7a8c4
> > > Author: Bart Van Assche <bvanassche@xxxxxxx>
> > > 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)?
> 
> Had you already noticed the following message?
> 
> https://lore.kernel.org/bpf/d76d7a63-7854-e92d-30cb-52546d333ffe@xxxxxxxxxxxxx/
> 
> 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!"

Apologies, but I hadn't received that when I sent my initial email. Anyway,
just wanted to make sure somebody was looking into it!

Will