Hello,
syzbot found the following issue on:
HEAD commit:b28241d8 Add linux-next specific files for 20210127
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13316b44d0
kernel config: https://syzkaller.appspot.com/x/.config?x=37c8f99c7210a867
dashboard
Hello,
syzbot found the following issue on:
HEAD commit:226871e2 Add linux-next specific files for 20210122
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1076afe750
kernel config: https://syzkaller.appspot.com/x/.config?x=40930d62519ae2bd
dashboard
Hello,
syzbot found the following issue on:
HEAD commit:cf7cd542 Add linux-next specific files for 20201104
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13b7bb8250
kernel config: https://syzkaller.appspot.com/x/.config?x=e8dc0c5ac73afb92
dashboard
On Thu, Jul 02, 2020 at 03:02:14AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:d37d5704 Add linux-next specific files for 20200702
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1549d0a310
> kernel
Hello,
syzbot found the following crash on:
HEAD commit:d37d5704 Add linux-next specific files for 20200702
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1549d0a310
kernel config: https://syzkaller.appspot.com/x/.config?x=a0a0972a399422ff
dashboard
#syz dup: net-next test error: KASAN: use-after-free Write in
afs_wake_up_async_call
Hello,
syzbot found the following crash on:
HEAD commit:64302eab Add linux-next specific files for 20200613
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17bc9eda10
kernel config: https://syzkaller.appspot.com/x/.config?x=a4b041729071d963
dashboard
On Fri, Jun 12, 2020 at 07:09:04PM +0530, Ritesh Harjani wrote:
> I see Ted has already taken v2 of this patch in his dev repo.
> Should be able to see in linux tree soon.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?h=dev=811985365378df01386c3cfb7ff716e74ca376d5
On 6/12/20 6:13 PM, Ido Schimmel wrote:
On Tue, Jun 02, 2020 at 06:11:29PM +0530, Ritesh Harjani wrote:
#syz test:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
0e21d4620dd047da7952f44a2e1ac777ded2d57e
>From cc1cf67d99d5fa61db0651c89c288df31bad6b8e Mon Sep 17 00:00:00
On Tue, Jun 02, 2020 at 06:11:29PM +0530, Ritesh Harjani wrote:
> #syz test:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> 0e21d4620dd047da7952f44a2e1ac777ded2d57e
> >From cc1cf67d99d5fa61db0651c89c288df31bad6b8e Mon Sep 17 00:00:00 2001
> From: Ritesh Harjani
> Date:
generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with sy
-
> This bug is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to co
generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with sy
y contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
#syz dup: linux-nex
1690 kernel/workqueue.c:2269
> worker_thread+0x96/0xe10 kernel/workqueue.c:2415
> kthread+0x3b5/0x4a0 kernel/kthread.c:291
> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> tipc: TX() has been purged, node left!
>
>
> ---
> This bug is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
--
Cheers,
Stephen Rothwell
pgpmLPZurlm82.pgp
Description: OpenPGP digital signature
read+0x3b5/0x4a0 kernel/kthread.c:291
> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> tipc: TX() has been purged, node left!
>
>
> ---
> This bug is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkal...@googlegroups.com.
>
> syzbot will keep track of this bug report. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
--
Cheers,
Stephen Rothwell
pgpjoF9iPF3Hh.pgp
Description: OpenPGP digital signature
Hello,
syzbot found the following crash on:
HEAD commit:af30725c Add linux-next specific files for 20200605
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=126f99a610
kernel config: https://syzkaller.appspot.com/x/.config?x=579d800cf0c74ef
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:48f99181 Add linux-next specific files for 20200603
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=148e22f210
kernel config: https://syzkaller.appspot.com/x/.config?x=365f706273eaf502
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:48f99181 Add linux-next specific files for 20200603
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16a4c05110
kernel config: https://syzkaller.appspot.com/x/.config?x=365f706273eaf502
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:48f99181 Add linux-next specific files for 20200603
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1006bca610
kernel config: https://syzkaller.appspot.com/x/.config?x=365f706273eaf502
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1461fcf210
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=107072f210
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
back.c:2079
> process_one_work+0x965/0x1690 kernel/workqueue.c:2269
> worker_thread+0x96/0xe10 kernel/workqueue.c:2415
> kthread+0x3b5/0x4a0 kernel/kthread.c:291
> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
01ed RDI: 55fab378a985
> RBP: 7fe0d32c9680 R08: 0100 R09:
> R10: 55fab378a980 R11: 00000246 R12: 01ed
> R13: 7fffd5e80610 R14: R15:
>
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
e0 RDI: ff9c
> RBP: 00ccf510 R08: R09:
> R10: R11: 00000212 R12:
> R13: 0060 R14: 005f R15: 0100
>
>
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
01ed RDI: 5647ba692985
> RBP: 7fa49b78d680 R08: 0100 R09:
> R10: 5647ba692980 R11: 00000246 R12: 01ed
> R13: 7ffde4438460 R14: R15:
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
C
> handling
>
Hmm, syzbot reported this several times already. Marking it as a duplicate
of the report where the discussion happened:
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
- Eric
process_one_work+0x965/0x1690 kernel/workqueue.c:2269
> worker_thread+0x96/0xe10 kernel/workqueue.c:2415
> kthread+0x3b5/0x4a0 kernel/kthread.c:291
> ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293
> tipc: TX() has been purged, node left!
#syz dup: linux-next test error: BUG: using smp_processor_id() in preemptible
[ADDR] code: syz-fuzzer/6792
Introduced by:
commit 42f56b7a4a7db127a9d281da584152dc3d525d25
Author: Ritesh Harjani
Date: Wed May 20 12:10:34 2020 +0530
ext4: mballoc: introduce pcpu seqcnt for freeing PA to improve ENOSPC
handling
On Thu, Jun 04, 2020 at 07:02:18PM -0700, syzbot wrote:
> Hello,
>
> syzbot found
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1046166110
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
On 6/2/20 8:22 PM, Hillf Danton wrote:
Tue, 02 Jun 2020 04:20:16 -0700
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=127233ee10
kernel config:
#syz test:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
0e21d4620dd047da7952f44a2e1ac777ded2d57e
>From cc1cf67d99d5fa61db0651c89c288df31bad6b8e Mon Sep 17 00:00:00 2001
From: Ritesh Harjani
Date: Tue, 2 Jun 2020 17:54:12 +0530
Subject: [PATCH 1/1] ext4: mballoc: Use
> #syz test:
This crash does not have a reproducer. I cannot test it.
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> 0e21d4620dd047da7952f44a2e1ac777ded2d57e
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=102c59ce10
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13f3dcca10
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13a7ffe210
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17fee51610
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=127233ee10
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e21d462 Add linux-next specific files for 20200602
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1597f2fe10
kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3
dashboard
On Tue, 22 Oct 2019 15:44:12 -0700 syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:a722f75b Add linux-next specific files for 20191022
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=126aea5b60
> kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:a722f75b Add linux-next specific files for 20191022
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=126aea5b60
kernel config: https://syzkaller.appspot.com/x/.config?x=32434321999f01e9
Hello,
syzbot found the following crash on:
HEAD commit:340ae71f9dd4 Add linux-next specific files for 20181221
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11d9566740
kernel config: https://syzkaller.appspot.com/x/.config?x=c190b602a5d2d731
On Thu, Sep 06, 2018 at 09:12:12AM -0400, Theodore Y. Ts'o wrote:
> So I don't see the point of changing return value block_page_mkwrite()
> (although to be honest I haven't see the value of the vm_fault_t
> change at all in the first place, at least not compared to the pain it
> has caused) but
On Thu, Sep 06, 2018 at 09:12:12AM -0400, Theodore Y. Ts'o wrote:
> So I don't see the point of changing return value block_page_mkwrite()
> (although to be honest I haven't see the value of the vm_fault_t
> change at all in the first place, at least not compared to the pain it
> has caused) but
P.S. This is the second time the vm_fualt_t change has broken things.
The first time, when it went through the ext4 tree, I NACK'ed it after
a 60 seconds smoke test showed it was broken. This time it went
through the mm tree...
In the future, even for "trivial" changes, could you *please* run
P.S. This is the second time the vm_fualt_t change has broken things.
The first time, when it went through the ext4 tree, I NACK'ed it after
a 60 seconds smoke test showed it was broken. This time it went
through the mm tree...
In the future, even for "trivial" changes, could you *please* run
On Thu, Sep 06, 2018 at 05:56:31PM +0530, Souptick Joarder wrote:
> > Yes, I'd start with converting ext4_page_mkwrite() - that should be pretty
> > straightforward - and we can leave block_page_mkwrite() as is for now. I
> > don't think allocating other VM_FAULT_ codes is going to cut it as
> >
On Thu, Sep 06, 2018 at 05:56:31PM +0530, Souptick Joarder wrote:
> > Yes, I'd start with converting ext4_page_mkwrite() - that should be pretty
> > straightforward - and we can leave block_page_mkwrite() as is for now. I
> > don't think allocating other VM_FAULT_ codes is going to cut it as
> >
On Thu, Sep 06, 2018 at 05:56:31PM +0530, Souptick Joarder wrote:
> On Thu, Sep 6, 2018 at 2:08 PM Jan Kara wrote:
> > Yes, I'd start with converting ext4_page_mkwrite() - that should be pretty
> > straightforward - and we can leave block_page_mkwrite() as is for now. I
> > don't think allocating
On Thu, Sep 06, 2018 at 05:56:31PM +0530, Souptick Joarder wrote:
> On Thu, Sep 6, 2018 at 2:08 PM Jan Kara wrote:
> > Yes, I'd start with converting ext4_page_mkwrite() - that should be pretty
> > straightforward - and we can leave block_page_mkwrite() as is for now. I
> > don't think allocating
On Thu, Sep 6, 2018 at 2:08 PM Jan Kara wrote:
>
> On Thu 06-09-18 00:54:50, Souptick Joarder wrote:
> > On Wed, Sep 5, 2018 at 7:05 PM Theodore Y. Ts'o wrote:
> > >
> > > On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
> > > >
> > > > "fs: convert return type int to
On Thu, Sep 6, 2018 at 2:08 PM Jan Kara wrote:
>
> On Thu 06-09-18 00:54:50, Souptick Joarder wrote:
> > On Wed, Sep 5, 2018 at 7:05 PM Theodore Y. Ts'o wrote:
> > >
> > > On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
> > > >
> > > > "fs: convert return type int to
On Thu, Sep 6, 2018 at 1:42 PM Jan Kara wrote:
>
> On Thu 06-09-18 00:37:06, Souptick Joarder wrote:
> > On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
> > >
> > > On Wed 05-09-18 00:13:02, syzbot wrote:
> > > > Hello,
> > > >
> > > > syzbot found the following crash on:
> > > >
> > > > HEAD
On Thu, Sep 6, 2018 at 1:42 PM Jan Kara wrote:
>
> On Thu 06-09-18 00:37:06, Souptick Joarder wrote:
> > On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
> > >
> > > On Wed 05-09-18 00:13:02, syzbot wrote:
> > > > Hello,
> > > >
> > > > syzbot found the following crash on:
> > > >
> > > > HEAD
On Thu 06-09-18 00:54:50, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 7:05 PM Theodore Y. Ts'o wrote:
> >
> > On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
> > >
> > > "fs: convert return type int to vm_fault_t" is still under
> > > review/discusson and not yet merge
> >
On Thu 06-09-18 00:54:50, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 7:05 PM Theodore Y. Ts'o wrote:
> >
> > On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
> > >
> > > "fs: convert return type int to vm_fault_t" is still under
> > > review/discusson and not yet merge
> >
On Thu 06-09-18 00:37:06, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
> >
> > On Wed 05-09-18 00:13:02, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> >
On Thu 06-09-18 00:37:06, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
> >
> > On Wed 05-09-18 00:13:02, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> >
On Wed, Sep 5, 2018 at 7:05 PM Theodore Y. Ts'o wrote:
>
> On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
> >
> > "fs: convert return type int to vm_fault_t" is still under
> > review/discusson and not yet merge
> > into linux-next. I am not seeing it into linux-next tree.Can
On Wed, Sep 5, 2018 at 7:05 PM Theodore Y. Ts'o wrote:
>
> On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
> >
> > "fs: convert return type int to vm_fault_t" is still under
> > review/discusson and not yet merge
> > into linux-next. I am not seeing it into linux-next tree.Can
On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>
> On Wed 05-09-18 00:13:02, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> > git tree: linux-next
> > console output:
On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>
> On Wed 05-09-18 00:13:02, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> > git tree: linux-next
> > console output:
On Wed, Sep 05, 2018 at 09:34:59AM -0400, Theodore Y. Ts'o wrote:
> It's at: 83c0adddcc6ed128168e7b87eaed0c21eac908e4 in the Linux Next
> branch.
>
> Dmitry, can you try reverting this commit and see if it makes the
> problem go away?
>
> Souptick, can we just NACK this patch and completely drop
On Wed, Sep 05, 2018 at 09:34:59AM -0400, Theodore Y. Ts'o wrote:
> It's at: 83c0adddcc6ed128168e7b87eaed0c21eac908e4 in the Linux Next
> branch.
>
> Dmitry, can you try reverting this commit and see if it makes the
> problem go away?
>
> Souptick, can we just NACK this patch and completely drop
On Wed 05-09-18 15:20:16, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
> >
> > On Wed 05-09-18 00:13:02, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> >
On Wed 05-09-18 15:20:16, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
> >
> > On Wed 05-09-18 00:13:02, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> >
On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
>
> "fs: convert return type int to vm_fault_t" is still under
> review/discusson and not yet merge
> into linux-next. I am not seeing it into linux-next tree.Can you
> please share the commit id ?
It's at:
On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
>
> "fs: convert return type int to vm_fault_t" is still under
> review/discusson and not yet merge
> into linux-next. I am not seeing it into linux-next tree.Can you
> please share the commit id ?
It's at:
On Wed, Sep 5, 2018 at 11:53 AM, Dmitry Vyukov wrote:
> On Wed, Sep 5, 2018 at 11:50 AM, Souptick Joarder
> wrote:
>> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>>>
>>> On Wed 05-09-18 00:13:02, syzbot wrote:
>>> > Hello,
>>> >
>>> > syzbot found the following crash on:
>>> >
>>> > HEAD
On Wed, Sep 5, 2018 at 11:53 AM, Dmitry Vyukov wrote:
> On Wed, Sep 5, 2018 at 11:50 AM, Souptick Joarder
> wrote:
>> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>>>
>>> On Wed 05-09-18 00:13:02, syzbot wrote:
>>> > Hello,
>>> >
>>> > syzbot found the following crash on:
>>> >
>>> > HEAD
On Wed, Sep 5, 2018 at 11:50 AM, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>>
>> On Wed 05-09-18 00:13:02, syzbot wrote:
>> > Hello,
>> >
>> > syzbot found the following crash on:
>> >
>> > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
>>
On Wed, Sep 5, 2018 at 11:50 AM, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>>
>> On Wed 05-09-18 00:13:02, syzbot wrote:
>> > Hello,
>> >
>> > syzbot found the following crash on:
>> >
>> > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
>>
On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>
> On Wed 05-09-18 00:13:02, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> > git tree: linux-next
> > console output:
On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
>
> On Wed 05-09-18 00:13:02, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> > git tree: linux-next
> > console output:
On Wed 05-09-18 00:13:02, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=149c67a640
> kernel config:
On Wed 05-09-18 00:13:02, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=149c67a640
> kernel config:
On Wed, Sep 5, 2018 at 9:13 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=149c67a640
> kernel config:
On Wed, Sep 5, 2018 at 9:13 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=149c67a640
> kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=149c67a640
kernel config: https://syzkaller.appspot.com/x/.config?x=ad5163873ecfbc32
Hello,
syzbot found the following crash on:
HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=149c67a640
kernel config: https://syzkaller.appspot.com/x/.config?x=ad5163873ecfbc32
80 matches
Mail list logo
