Re: WARNING in __kernel_read (2)

2020-09-29 Thread Christoph Hellwig
On Tue, Sep 29, 2020 at 10:21:19AM +0200, Dmitry Vyukov wrote: > On Tue, Sep 29, 2020 at 10:06 AM David Laight wrote: > > > > From: Christoph Hellwig > > > Sent: 29 September 2020 07:56 > > > > > > On Mon, Sep 28, 2020 at 11:46:48PM -0700, Eric Biggers wrote: > > > > > Linus asked for it. What is

Re: WARNING in __kernel_read (2)

2020-09-29 Thread Dmitry Vyukov
On Tue, Sep 29, 2020 at 10:06 AM David Laight wrote: > > From: Christoph Hellwig > > Sent: 29 September 2020 07:56 > > > > On Mon, Sep 28, 2020 at 11:46:48PM -0700, Eric Biggers wrote: > > > > Linus asked for it. What is the call chain that we hit it with? > > > > > > Call Trace: > > > kernel_re

RE: WARNING in __kernel_read (2)

2020-09-29 Thread David Laight
From: Christoph Hellwig > Sent: 29 September 2020 07:56 > > On Mon, Sep 28, 2020 at 11:46:48PM -0700, Eric Biggers wrote: > > > Linus asked for it. What is the call chain that we hit it with? > > > > Call Trace: > > kernel_read+0x52/0x70 fs/read_write.c:471 > > kernel_read_file fs/exec.c:989 [i

Re: WARNING in __kernel_read (2)

2020-09-28 Thread Christoph Hellwig
On Mon, Sep 28, 2020 at 11:46:48PM -0700, Eric Biggers wrote: > > Linus asked for it. What is the call chain that we hit it with? > > Call Trace: > kernel_read+0x52/0x70 fs/read_write.c:471 > kernel_read_file fs/exec.c:989 [inline] > kernel_read_file+0x2e5/0x620 fs/exec.c:952 > kernel_read_fi

Re: WARNING in __kernel_read (2)

2020-09-28 Thread Eric Biggers
t; > > To: 'syzbot' ; > > > > linux-fsde...@vger.kernel.org; > > > > linux-kernel@vger.kernel.org; syzkaller-b...@googlegroups.com; > > > > v...@zeniv.linux.org.uk > > > > Subject: RE: WARNING in __kernel_read (2) > > > &

Re: WARNING in __kernel_read (2)

2020-09-28 Thread Christoph Hellwig
gt; > > linux-kernel@vger.kernel.org; syzkaller-b...@googlegroups.com; > > > v...@zeniv.linux.org.uk > > > Subject: RE: WARNING in __kernel_read (2) > > > > > > > From: syzbot > > > > Sent: 26 September 2020 03:58 > > > >

Re: WARNING in __kernel_read (2)

2020-09-28 Thread Eric Biggers
iv.linux.org.uk > > Subject: RE: WARNING in __kernel_read (2) > > > > > From: syzbot > > > Sent: 26 September 2020 03:58 > > > To: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org; > > > syzkaller-b...@googlegroups.com; > > > v.

RE: WARNING in __kernel_read (2)

2020-09-26 Thread David Laight
From: David Laight > Sent: 26 September 2020 12:16 > To: 'syzbot' ; > linux-fsde...@vger.kernel.org; > linux-kernel@vger.kernel.org; syzkaller-b...@googlegroups.com; > v...@zeniv.linux.org.uk > Subject: RE: WARNING in __kernel_read (2) > > > From: syzb

RE: WARNING in __kernel_read (2)

2020-09-26 Thread David Laight
> From: syzbot > Sent: 26 September 2020 03:58 > To: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org; > syzkaller-b...@googlegroups.com; > v...@zeniv.linux.org.uk > Subject: WARNING in __kernel_read (2) I suspect this is calling finit_module() on an fd that

WARNING in __kernel_read (2)

2020-09-25 Thread syzbot
Hello, syzbot found the following issue on: HEAD commit:b10b8ad8 Add linux-next specific files for 20200921 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1437eff190 kernel config: https://syzkaller.appspot.com/x/.config?x=3cf0782933432b43 dashboard