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
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:
> > >
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
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
>
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)
> > > >
>
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
> > > > To: linu
x.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...@zeniv.l
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: syzbot
> &
> 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
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
Hi Cengiz,
On Thu, Jul 23, 2020 at 05:17:25PM +0300, Cengiz Can wrote:
> Hello,
>
> I'm trying to help clean up syzkaller submissions and this caught my
> attention and I wanted to get your advice.
>
> With commit: 6209dd9132e8ea5545cffc84483841e88ea8cc5b `kernel_read` was
> modified to use
t; > https://syzkaller.appspot.com/x/report.txt?x=172d91fb10
> > console output:
> > https://syzkaller.appspot.com/x/log.txt?x=132d91fb10
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the
> > commit:
> > Reported-by: syzbot+d012
ler.appspot.com/x/report.txt?x=172d91fb10
> console output: https://syzkaller.appspot.com/x/log.txt?x=132d91fb10
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+d012ca3f813739c37...@syzkaller.appspotmail.com
> Fixes: 6209dd
=172d91fb10
console output: https://syzkaller.appspot.com/x/log.txt?x=132d91fb10
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+d012ca3f813739c37...@syzkaller.appspotmail.com
Fixes: 6209dd9132e8 ("fs: implement kernel_read using __kernel
14 matches
Mail list logo
