All of lore.kernel.org
 help / color / mirror / Atom feed
* [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread
@ 2022-10-13  8:05 ` syzbot
  0 siblings, 0 replies; 6+ messages in thread
From: syzbot @ 2022-10-13  8:05 UTC (permalink / raw)
  To: chao, jaegeuk, linux-f2fs-devel, linux-kernel, syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    bbed346d5a96 Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=13615406880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3a4a45d2d827c1e
dashboard link: https://syzkaller.appspot.com/bug?extid=035a381ea1afb63f098d
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15281162880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=137aa942880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e8e91bc79312/disk-bbed346d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1cb3fb3b77e/vmlinux-bbed346d.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/eb56ba4877e7/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 264192
F2FS-fs (loop0): invalid crc_offset: 0
F2FS-fs (loop0): Found nat_bits in checkpoint
F2FS-fs (loop0): Mounted with checkpoint version = 3651456e
Unable to handle kernel NULL pointer dereference at virtual address 000000000000001c
Mem abort info:
  ESR = 0x0000000096000004
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x04: level 0 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000004
  CM = 0, WnR = 0
user pgtable: 4k pages, 48-bit VAs, pgdp=000000010899a000
[000000000000001c] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 3029 Comm: syz-executor654 Not tainted 6.0.0-rc7-syzkaller-18095-gbbed346d5a96 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __lse_atomic_fetch_add_relaxed arch/arm64/include/asm/atomic_lse.h:62 [inline]
pc : arch_atomic_fetch_add_relaxed arch/arm64/include/asm/atomic.h:49 [inline]
pc : atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:117 [inline]
pc : __refcount_add include/linux/refcount.h:193 [inline]
pc : __refcount_inc include/linux/refcount.h:250 [inline]
pc : refcount_inc include/linux/refcount.h:267 [inline]
pc : get_task_struct include/linux/sched/task.h:110 [inline]
pc : kthread_stop+0x34/0x1c0 kernel/kthread.c:703
lr : __refcount_add include/linux/refcount.h:193 [inline]
lr : __refcount_inc include/linux/refcount.h:250 [inline]
lr : refcount_inc include/linux/refcount.h:267 [inline]
lr : get_task_struct include/linux/sched/task.h:110 [inline]
lr : kthread_stop+0x30/0x1c0 kernel/kthread.c:703
sp : ffff8000128abb60
x29: ffff8000128abb60 x28: 0000000000000000 x27: 000000000000007e
x26: ffff80000d30cf28 x25: ffff80000d309000 x24: 0000000000000008
x23: ffffffffffffffff x22: 0000000000000000 x21: 0000000000000000
x20: fffffffffffffff4 x19: 000000000000001c x18: 00000000000000c0
x17: ffff80000dd0b198 x16: ffff80000db49158 x15: ffff0000c665cf80
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c665cf80
x11: ff808000081403c0 x10: 0000000000000000 x9 : ffff8000081403c0
x8 : 0000000000000001 x7 : ffff8000095d331c x6 : 0000000000000000
x5 : 000000008010000f x4 : fffffc00032f6a20 x3 : 000000008010000f
x2 : ffff0000cbda8100 x1 : 0000000100000000 x0 : 0000000000000000
Call trace:
 __refcount_add include/linux/refcount.h:193 [inline]
 __refcount_inc include/linux/refcount.h:250 [inline]
 refcount_inc include/linux/refcount.h:267 [inline]
 get_task_struct include/linux/sched/task.h:110 [inline]
 kthread_stop+0x34/0x1c0 kernel/kthread.c:703
 f2fs_stop_discard_thread+0x3c/0x5c fs/f2fs/segment.c:1638
 kill_f2fs_super+0x5c/0x194 fs/f2fs/super.c:4522
 deactivate_locked_super+0x70/0xe8 fs/super.c:332
 deactivate_super+0xd0/0xd4 fs/super.c:363
 cleanup_mnt+0x1f8/0x234 fs/namespace.c:1186
 __cleanup_mnt+0x20/0x30 fs/namespace.c:1193
 task_work_run+0xc4/0x14c kernel/task_work.c:177
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x26c/0xbe0 kernel/exit.c:795
 do_group_exit+0x60/0xe8 kernel/exit.c:925
 __do_sys_exit_group kernel/exit.c:936 [inline]
 __se_sys_exit_group kernel/exit.c:934 [inline]
 __wake_up_parent+0x0/0x40 kernel/exit.c:934
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
 el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: 9100a293 d503201f 94057e16 52800028 (b8280275) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	9100a293 	add	x19, x20, #0x28
   4:	d503201f 	nop
   8:	94057e16 	bl	0x15f860
   c:	52800028 	mov	w8, #0x1                   	// #1
* 10:	b8280275 	ldadd	w8, w21, [x19] <-- trapping instruction


---
This report 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 syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [f2fs-dev] [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread
@ 2022-10-13  8:05 ` syzbot
  0 siblings, 0 replies; 6+ messages in thread
From: syzbot @ 2022-10-13  8:05 UTC (permalink / raw)
  To: chao, jaegeuk, linux-f2fs-devel, linux-kernel, syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    bbed346d5a96 Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=13615406880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3a4a45d2d827c1e
dashboard link: https://syzkaller.appspot.com/bug?extid=035a381ea1afb63f098d
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=15281162880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=137aa942880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e8e91bc79312/disk-bbed346d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1cb3fb3b77e/vmlinux-bbed346d.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/eb56ba4877e7/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 264192
F2FS-fs (loop0): invalid crc_offset: 0
F2FS-fs (loop0): Found nat_bits in checkpoint
F2FS-fs (loop0): Mounted with checkpoint version = 3651456e
Unable to handle kernel NULL pointer dereference at virtual address 000000000000001c
Mem abort info:
  ESR = 0x0000000096000004
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x04: level 0 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000004
  CM = 0, WnR = 0
user pgtable: 4k pages, 48-bit VAs, pgdp=000000010899a000
[000000000000001c] pgd=0000000000000000, p4d=0000000000000000
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 3029 Comm: syz-executor654 Not tainted 6.0.0-rc7-syzkaller-18095-gbbed346d5a96 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __lse_atomic_fetch_add_relaxed arch/arm64/include/asm/atomic_lse.h:62 [inline]
pc : arch_atomic_fetch_add_relaxed arch/arm64/include/asm/atomic.h:49 [inline]
pc : atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:117 [inline]
pc : __refcount_add include/linux/refcount.h:193 [inline]
pc : __refcount_inc include/linux/refcount.h:250 [inline]
pc : refcount_inc include/linux/refcount.h:267 [inline]
pc : get_task_struct include/linux/sched/task.h:110 [inline]
pc : kthread_stop+0x34/0x1c0 kernel/kthread.c:703
lr : __refcount_add include/linux/refcount.h:193 [inline]
lr : __refcount_inc include/linux/refcount.h:250 [inline]
lr : refcount_inc include/linux/refcount.h:267 [inline]
lr : get_task_struct include/linux/sched/task.h:110 [inline]
lr : kthread_stop+0x30/0x1c0 kernel/kthread.c:703
sp : ffff8000128abb60
x29: ffff8000128abb60 x28: 0000000000000000 x27: 000000000000007e
x26: ffff80000d30cf28 x25: ffff80000d309000 x24: 0000000000000008
x23: ffffffffffffffff x22: 0000000000000000 x21: 0000000000000000
x20: fffffffffffffff4 x19: 000000000000001c x18: 00000000000000c0
x17: ffff80000dd0b198 x16: ffff80000db49158 x15: ffff0000c665cf80
x14: 0000000000000000 x13: 00000000ffffffff x12: ffff0000c665cf80
x11: ff808000081403c0 x10: 0000000000000000 x9 : ffff8000081403c0
x8 : 0000000000000001 x7 : ffff8000095d331c x6 : 0000000000000000
x5 : 000000008010000f x4 : fffffc00032f6a20 x3 : 000000008010000f
x2 : ffff0000cbda8100 x1 : 0000000100000000 x0 : 0000000000000000
Call trace:
 __refcount_add include/linux/refcount.h:193 [inline]
 __refcount_inc include/linux/refcount.h:250 [inline]
 refcount_inc include/linux/refcount.h:267 [inline]
 get_task_struct include/linux/sched/task.h:110 [inline]
 kthread_stop+0x34/0x1c0 kernel/kthread.c:703
 f2fs_stop_discard_thread+0x3c/0x5c fs/f2fs/segment.c:1638
 kill_f2fs_super+0x5c/0x194 fs/f2fs/super.c:4522
 deactivate_locked_super+0x70/0xe8 fs/super.c:332
 deactivate_super+0xd0/0xd4 fs/super.c:363
 cleanup_mnt+0x1f8/0x234 fs/namespace.c:1186
 __cleanup_mnt+0x20/0x30 fs/namespace.c:1193
 task_work_run+0xc4/0x14c kernel/task_work.c:177
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x26c/0xbe0 kernel/exit.c:795
 do_group_exit+0x60/0xe8 kernel/exit.c:925
 __do_sys_exit_group kernel/exit.c:936 [inline]
 __se_sys_exit_group kernel/exit.c:934 [inline]
 __wake_up_parent+0x0/0x40 kernel/exit.c:934
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
 el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: 9100a293 d503201f 94057e16 52800028 (b8280275) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	9100a293 	add	x19, x20, #0x28
   4:	d503201f 	nop
   8:	94057e16 	bl	0x15f860
   c:	52800028 	mov	w8, #0x1                   	// #1
* 10:	b8280275 	ldadd	w8, w21, [x19] <-- trapping instruction


---
This report 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 syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread
  2022-10-13  8:05 ` [f2fs-dev] " syzbot
@ 2022-10-28  3:34   ` syzbot
  -1 siblings, 0 replies; 6+ messages in thread
From: syzbot @ 2022-10-28  3:34 UTC (permalink / raw)
  To: changfengnan, chao, frank.li, jaegeuk, linux-f2fs-devel,
	linux-kernel, syzkaller-bugs, wuhoipok

syzbot has bisected this issue to:

commit 4d67490498acb4ffcef5ba7bc44990d46e66a44c
Author: Fengnan Chang <changfengnan@vivo.com>
Date:   Thu Aug 19 08:02:37 2021 +0000

    f2fs: Don't create discard thread when device doesn't support realtime discard

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17da7522880000
start commit:   247f34f7b803 Linux 6.1-rc2
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=143a7522880000
console output: https://syzkaller.appspot.com/x/log.txt?x=103a7522880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=035a381ea1afb63f098d
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11d92d6a880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12e5dbba880000

Reported-by: syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com
Fixes: 4d67490498ac ("f2fs: Don't create discard thread when device doesn't support realtime discard")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [f2fs-dev] [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread
@ 2022-10-28  3:34   ` syzbot
  0 siblings, 0 replies; 6+ messages in thread
From: syzbot @ 2022-10-28  3:34 UTC (permalink / raw)
  To: changfengnan, chao, frank.li, jaegeuk, linux-f2fs-devel,
	linux-kernel, syzkaller-bugs, wuhoipok

syzbot has bisected this issue to:

commit 4d67490498acb4ffcef5ba7bc44990d46e66a44c
Author: Fengnan Chang <changfengnan@vivo.com>
Date:   Thu Aug 19 08:02:37 2021 +0000

    f2fs: Don't create discard thread when device doesn't support realtime discard

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17da7522880000
start commit:   247f34f7b803 Linux 6.1-rc2
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=143a7522880000
console output: https://syzkaller.appspot.com/x/log.txt?x=103a7522880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=035a381ea1afb63f098d
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11d92d6a880000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12e5dbba880000

Reported-by: syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com
Fixes: 4d67490498ac ("f2fs: Don't create discard thread when device doesn't support realtime discard")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [f2fs-dev] [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread
  2022-10-28  3:34   ` [f2fs-dev] " syzbot
@ 2022-10-28  3:49     ` Chao Yu
  -1 siblings, 0 replies; 6+ messages in thread
From: Chao Yu @ 2022-10-28  3:49 UTC (permalink / raw)
  To: syzbot, changfengnan, frank.li, jaegeuk, linux-f2fs-devel,
	linux-kernel, syzkaller-bugs, wuhoipok

Hello,

Thanks for the report, the bug has been fixed w/ below patch:

https://lore.kernel.org/linux-f2fs-devel/20221021023422.3101585-1-chao@kernel.org/T/#u

On 2022/10/28 11:34, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit 4d67490498acb4ffcef5ba7bc44990d46e66a44c
> Author: Fengnan Chang <changfengnan@vivo.com>
> Date:   Thu Aug 19 08:02:37 2021 +0000
> 
>      f2fs: Don't create discard thread when device doesn't support realtime discard
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17da7522880000
> start commit:   247f34f7b803 Linux 6.1-rc2
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=143a7522880000
> console output: https://syzkaller.appspot.com/x/log.txt?x=103a7522880000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
> dashboard link: https://syzkaller.appspot.com/bug?extid=035a381ea1afb63f098d
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11d92d6a880000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12e5dbba880000
> 
> Reported-by: syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com
> Fixes: 4d67490498ac ("f2fs: Don't create discard thread when device doesn't support realtime discard")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [f2fs-dev] [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread
@ 2022-10-28  3:49     ` Chao Yu
  0 siblings, 0 replies; 6+ messages in thread
From: Chao Yu @ 2022-10-28  3:49 UTC (permalink / raw)
  To: syzbot, changfengnan, frank.li, jaegeuk, linux-f2fs-devel,
	linux-kernel, syzkaller-bugs, wuhoipok

Hello,

Thanks for the report, the bug has been fixed w/ below patch:

https://lore.kernel.org/linux-f2fs-devel/20221021023422.3101585-1-chao@kernel.org/T/#u

On 2022/10/28 11:34, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit 4d67490498acb4ffcef5ba7bc44990d46e66a44c
> Author: Fengnan Chang <changfengnan@vivo.com>
> Date:   Thu Aug 19 08:02:37 2021 +0000
> 
>      f2fs: Don't create discard thread when device doesn't support realtime discard
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17da7522880000
> start commit:   247f34f7b803 Linux 6.1-rc2
> git tree:       upstream
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=143a7522880000
> console output: https://syzkaller.appspot.com/x/log.txt?x=103a7522880000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
> dashboard link: https://syzkaller.appspot.com/bug?extid=035a381ea1afb63f098d
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11d92d6a880000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12e5dbba880000
> 
> Reported-by: syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com
> Fixes: 4d67490498ac ("f2fs: Don't create discard thread when device doesn't support realtime discard")
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
> 
> 
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2022-10-28  3:49 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-13  8:05 [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread syzbot
2022-10-13  8:05 ` [f2fs-dev] " syzbot
2022-10-28  3:34 ` syzbot
2022-10-28  3:34   ` [f2fs-dev] " syzbot
2022-10-28  3:49   ` Chao Yu
2022-10-28  3:49     ` Chao Yu

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.