* [syzbot] [btrfs?] kernel BUG in clear_inode
@ 2024-05-31 18:56 syzbot
2024-06-07 5:05 ` syzbot
0 siblings, 1 reply; 9+ messages in thread
From: syzbot @ 2024-05-31 18:56 UTC (permalink / raw)
To: clm, dsterba, josef, linux-btrfs, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 2bfcfd584ff5 Merge tag 'pmdomain-v6.10-rc1' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=128ea8b4980000
kernel config: https://syzkaller.appspot.com/x/.config?x=733cc7a95171d8e7
dashboard link: https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-2bfcfd58.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c7ed3bb80bed/vmlinux-2bfcfd58.xz
kernel image: https://storage.googleapis.com/syzbot-assets/93acc5bfbaef/bzImage-2bfcfd58.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/inode.c:626!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 0 PID: 7700 Comm: syz-executor.2 Not tainted 6.10.0-rc1-syzkaller-00013-g2bfcfd584ff5 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 1e 7e 8b ff 90 0f 0b e8 16 7e 8b ff 90 0f 0b e8 0e 7e 8b ff 90 0f 0b e8 06 7e 8b ff 90 <0f> 0b e8 fe 7d 8b ff 90 0f 0b e8 b6 b0 e8 ff e9 d2 fe ff ff e8 ac
RSP: 0018:ffffc90003a2fab0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888028014230 RCX: ffffffff82030100
RDX: ffff88801e1fa440 RSI: ffffffff8203016a RDI: 0000000000000007
RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
R13: ffff88802855c000 R14: 0000000000000000 R15: ffff888028014230
FS: 0000000000000000(0000) GS:ffff88802c000000(0063) knlGS:0000000056b5e400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 00007f58c1d30980 CR3: 000000006b300000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000001000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_evict_inode+0x529/0xe80 fs/btrfs/inode.c:5262
evict+0x2ed/0x6c0 fs/inode.c:667
dispose_list+0x117/0x1e0 fs/inode.c:700
evict_inodes+0x34e/0x450 fs/inode.c:750
generic_shutdown_super+0xb5/0x3d0 fs/super.c:627
kill_anon_super+0x3a/0x60 fs/super.c:1226
btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2096
deactivate_locked_super+0xbe/0x1a0 fs/super.c:473
deactivate_super+0xde/0x100 fs/super.c:506
cleanup_mnt+0x222/0x450 fs/namespace.c:1267
task_work_run+0x14e/0x250 kernel/task_work.c:180
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x278/0x2a0 kernel/entry/common.c:218
__do_fast_syscall_32+0x80/0x120 arch/x86/entry/common.c:389
do_fast_syscall_32+0x32/0x80 arch/x86/entry/common.c:411
entry_SYSENTER_compat_after_hwframe+0x84/0x8e
RIP: 0023:0xf72c7579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000ff99b808 EFLAGS: 00000292 ORIG_RAX: 0000000000000034
RAX: 0000000000000000 RBX: 00000000ff99b8b0 RCX: 0000000000000009
RDX: 00000000f741dff4 RSI: 00000000f736e361 RDI: 00000000ff99c954
RBP: 00000000ff99b8b0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000296 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 1e 7e 8b ff 90 0f 0b e8 16 7e 8b ff 90 0f 0b e8 0e 7e 8b ff 90 0f 0b e8 06 7e 8b ff 90 <0f> 0b e8 fe 7d 8b ff 90 0f 0b e8 b6 b0 e8 ff e9 d2 fe ff ff e8 ac
RSP: 0018:ffffc90003a2fab0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888028014230 RCX: ffffffff82030100
RDX: ffff88801e1fa440 RSI: ffffffff8203016a RDI: 0000000000000007
RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
R13: ffff88802855c000 R14: 0000000000000000 R15: ffff888028014230
FS: 0000000000000000(0000) GS:ffff88802c000000(0063) knlGS:0000000056b5e400
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: 000000c000f9c4e0 CR3: 000000006b300000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000001000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 2 bytes skipped:
0: 10 06 adc %al,(%rsi)
2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi
6: 10 07 adc %al,(%rdi)
8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi
c: 10 08 adc %cl,(%rax)
e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi
1e: 00 51 52 add %dl,0x52(%rcx)
21: 55 push %rbp
22: 89 e5 mov %esp,%ebp
24: 0f 34 sysenter
26: cd 80 int $0x80
* 28: 5d pop %rbp <-- trapping instruction
29: 5a pop %rdx
2a: 59 pop %rcx
2b: c3 ret
2c: 90 nop
2d: 90 nop
2e: 90 nop
2f: 90 nop
30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-05-31 18:56 [syzbot] [btrfs?] kernel BUG in clear_inode syzbot
@ 2024-06-07 5:05 ` syzbot
2024-07-30 14:43 ` David Sterba
` (3 more replies)
0 siblings, 4 replies; 9+ messages in thread
From: syzbot @ 2024-06-07 5:05 UTC (permalink / raw)
To: clm, dsterba, josef, linux-btrfs, linux-kernel, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: d30d0e49da71 Merge tag 'net-6.10-rc3' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1736820a980000
kernel config: https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
dashboard link: https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a9aa22980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c57f16980000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-d30d0e49.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1276023ed77/vmlinux-d30d0e49.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a33f372d4fb8/bzImage-d30d0e49.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/7fc863ff127d/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/inode.c:626!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 1 PID: 5273 Comm: syz-executor331 Not tainted 6.10.0-rc2-syzkaller-00222-gd30d0e49da71 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
FS: 000055556268d380(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_evict_inode+0x529/0xe80 fs/btrfs/inode.c:5262
evict+0x2ed/0x6c0 fs/inode.c:667
dispose_list+0x117/0x1e0 fs/inode.c:700
evict_inodes+0x34e/0x450 fs/inode.c:750
generic_shutdown_super+0xb5/0x3d0 fs/super.c:627
kill_anon_super+0x3a/0x60 fs/super.c:1226
btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2096
deactivate_locked_super+0xbe/0x1a0 fs/super.c:473
deactivate_super+0xde/0x100 fs/super.c:506
cleanup_mnt+0x222/0x450 fs/namespace.c:1267
task_work_run+0x14e/0x250 kernel/task_work.c:180
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x278/0x2a0 kernel/entry/common.c:218
do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2ba3059777
Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fff42f9ee78 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f2ba3059777
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff42f9ef30
RBP: 00007fff42f9ef30 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 00007fff42f9ffa0
R13: 000055556268f6d0 R14: 431bde82d7b634db R15: 00007fff42f9ffc0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
FS: 000055556268d380(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-06-07 5:05 ` syzbot
@ 2024-07-30 14:43 ` David Sterba
2024-08-21 9:42 ` Julian Sun
` (2 subsequent siblings)
3 siblings, 0 replies; 9+ messages in thread
From: David Sterba @ 2024-07-30 14:43 UTC (permalink / raw)
To: syzbot; +Cc: clm, dsterba, josef, linux-btrfs, linux-kernel, syzkaller-bugs
On Thu, Jun 06, 2024 at 10:05:29PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: d30d0e49da71 Merge tag 'net-6.10-rc3' of git://git.kernel...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1736820a980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
> dashboard link: https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11a9aa22980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c57f16980000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-d30d0e49.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/f1276023ed77/vmlinux-d30d0e49.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/a33f372d4fb8/bzImage-d30d0e49.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/7fc863ff127d/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/inode.c:626!
BUG_ON(inode->i_state & I_CLEAR);
The bits are not manipulated directly in filesystems but the inode is in
a bad state in evict. The reported bug looks valid and there's a
reproducer.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-06-07 5:05 ` syzbot
2024-07-30 14:43 ` David Sterba
@ 2024-08-21 9:42 ` Julian Sun
2024-08-21 10:08 ` syzbot
2024-08-23 5:30 ` Julian Sun
2024-08-23 5:52 ` Julian Sun
3 siblings, 1 reply; 9+ messages in thread
From: Julian Sun @ 2024-08-21 9:42 UTC (permalink / raw)
To: syzbot; +Cc: clm, dsterba, josef, linux-btrfs, linux-kernel, syzkaller-bugs
On Thu, 2024-06-06 at 22:05 -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: d30d0e49da71 Merge tag 'net-6.10-rc3' of
> git://git.kernel...
> git tree: upstream
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=1736820a980000
> kernel config:
> https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils
> for Debian) 2.40
> syz repro:
> https://syzkaller.appspot.com/x/repro.syz?x=11a9aa22980000
> C reproducer:
> https://syzkaller.appspot.com/x/repro.c?x=14c57f16980000
>
> Downloadable assets:
> disk image (non-bootable):
> https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-d30d0e49.raw.xz
> vmlinux:
> https://storage.googleapis.com/syzbot-assets/f1276023ed77/vmlinux-d30d0e49.xz
> kernel image:
> https://storage.googleapis.com/syzbot-assets/a33f372d4fb8/bzImage-d30d0e49.xz
> mounted in repro:
> https://storage.googleapis.com/syzbot-assets/7fc863ff127d/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the
> commit:
> Reported-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/inode.c:626!
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
> CPU: 1 PID: 5273 Comm: syz-executor331 Not tainted 6.10.0-rc2-
> syzkaller-00222-gd30d0e49da71 #0
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-
> debian-1.16.2-1 04/01/2014
> RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
> Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8
> 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f>
> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
> RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
> RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
> RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
> R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
> R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
> FS: 000055556268d380(0000) GS:ffff88806b100000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> btrfs_evict_inode+0x529/0xe80 fs/btrfs/inode.c:5262
> evict+0x2ed/0x6c0 fs/inode.c:667
> dispose_list+0x117/0x1e0 fs/inode.c:700
> evict_inodes+0x34e/0x450 fs/inode.c:750
> generic_shutdown_super+0xb5/0x3d0 fs/super.c:627
> kill_anon_super+0x3a/0x60 fs/super.c:1226
> btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2096
> deactivate_locked_super+0xbe/0x1a0 fs/super.c:473
> deactivate_super+0xde/0x100 fs/super.c:506
> cleanup_mnt+0x222/0x450 fs/namespace.c:1267
> task_work_run+0x14e/0x250 kernel/task_work.c:180
> resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
> exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
> exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
> __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
> syscall_exit_to_user_mode+0x278/0x2a0 kernel/entry/common.c:218
> do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f2ba3059777
> Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66
> 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48>
> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
> RSP: 002b:00007fff42f9ee78 EFLAGS: 00000206 ORIG_RAX:
> 00000000000000a6
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f2ba3059777
> RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff42f9ef30
> RBP: 00007fff42f9ef30 R08: 0000000000000000 R09: 0000000000000000
> R10: 00000000ffffffff R11: 0000000000000206 R12: 00007fff42f9ffa0
> R13: 000055556268f6d0 R14: 431bde82d7b634db R15: 00007fff42f9ffc0
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
> Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8
> 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f>
> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
> RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
> RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
> RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
> R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
> R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
> FS: 000055556268d380(0000) GS:ffff88806b100000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>
>
> ---
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before
> testing.
Set the BTRFS_FS_CLOSING_START flag before kill_anon_super()
to prevent the race conditions between generic_shutdown_super()
and __btrfs_run_defrag_inode()
#syz test: upstream d30d0e49da71
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index f05cce7c8b8d..f7e87fe583ab 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -2093,6 +2093,7 @@ static int btrfs_get_tree(struct fs_context *fc)
static void btrfs_kill_super(struct super_block *sb)
{
struct btrfs_fs_info *fs_info = btrfs_sb(sb);
+ set_bit(BTRFS_FS_CLOSING_START, &fs_info->flags);
kill_anon_super(sb);
btrfs_free_fs_info(fs_info);
}
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-08-21 9:42 ` Julian Sun
@ 2024-08-21 10:08 ` syzbot
0 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2024-08-21 10:08 UTC (permalink / raw)
To: clm, dsterba, josef, linux-btrfs, linux-kernel, sunjunchao2870,
syzkaller-bugs
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
Tested-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
Tested on:
commit: d30d0e49 Merge tag 'net-6.10-rc3' of git://git.kernel...
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14fbfe05980000
kernel config: https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
dashboard link: https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17b31fbb980000
Note: testing is done by a robot and is best-effort only.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-06-07 5:05 ` syzbot
2024-07-30 14:43 ` David Sterba
2024-08-21 9:42 ` Julian Sun
@ 2024-08-23 5:30 ` Julian Sun
2024-08-23 5:32 ` syzbot
2024-08-23 5:52 ` Julian Sun
3 siblings, 1 reply; 9+ messages in thread
From: Julian Sun @ 2024-08-23 5:30 UTC (permalink / raw)
To: syzbot, clm, dsterba, josef, linux-btrfs, linux-kernel,
syzkaller-bugs
On Thu, 2024-06-06 at 22:05 -0700, syzbot wrote:
#syz test: upstream d30d0e49da71
diff --git a/fs/inode.c b/fs/inode.c
index 3a41f83a4ba5..011f630777d0 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -723,6 +723,10 @@ void evict_inodes(struct super_block *sb)
continue;
spin_lock(&inode->i_lock);
+ if (atomic_read(&inode->i_count)) {
+ spin_unlock(&inode->i_lock);
+ continue;
+ }
if (inode->i_state & (I_NEW | I_FREEING | I_WILL_FREE))
{
spin_unlock(&inode->i_lock);
continue;
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: d30d0e49da71 Merge tag 'net-6.10-rc3' of
> git://git.kernel...
> git tree: upstream
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=1736820a980000
> kernel config:
> https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils
> for Debian) 2.40
> syz repro:
> https://syzkaller.appspot.com/x/repro.syz?x=11a9aa22980000
> C reproducer:
> https://syzkaller.appspot.com/x/repro.c?x=14c57f16980000
>
> Downloadable assets:
> disk image (non-bootable):
> https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-d30d0e49.raw.xz
> vmlinux:
> https://storage.googleapis.com/syzbot-assets/f1276023ed77/vmlinux-d30d0e49.xz
> kernel image:
> https://storage.googleapis.com/syzbot-assets/a33f372d4fb8/bzImage-d30d0e49.xz
> mounted in repro:
> https://storage.googleapis.com/syzbot-assets/7fc863ff127d/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the
> commit:
> Reported-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/inode.c:626!
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
> CPU: 1 PID: 5273 Comm: syz-executor331 Not tainted 6.10.0-rc2-
> syzkaller-00222-gd30d0e49da71 #0
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-
> debian-1.16.2-1 04/01/2014
> RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
> Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8
> 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f>
> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
> RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
> RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
> RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
> R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
> R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
> FS: 000055556268d380(0000) GS:ffff88806b100000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> btrfs_evict_inode+0x529/0xe80 fs/btrfs/inode.c:5262
> evict+0x2ed/0x6c0 fs/inode.c:667
> dispose_list+0x117/0x1e0 fs/inode.c:700
> evict_inodes+0x34e/0x450 fs/inode.c:750
> generic_shutdown_super+0xb5/0x3d0 fs/super.c:627
> kill_anon_super+0x3a/0x60 fs/super.c:1226
> btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2096
> deactivate_locked_super+0xbe/0x1a0 fs/super.c:473
> deactivate_super+0xde/0x100 fs/super.c:506
> cleanup_mnt+0x222/0x450 fs/namespace.c:1267
> task_work_run+0x14e/0x250 kernel/task_work.c:180
> resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
> exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
> exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
> __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
> syscall_exit_to_user_mode+0x278/0x2a0 kernel/entry/common.c:218
> do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f2ba3059777
> Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66
> 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48>
> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
> RSP: 002b:00007fff42f9ee78 EFLAGS: 00000206 ORIG_RAX:
> 00000000000000a6
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f2ba3059777
> RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff42f9ef30
> RBP: 00007fff42f9ef30 R08: 0000000000000000 R09: 0000000000000000
> R10: 00000000ffffffff R11: 0000000000000206 R12: 00007fff42f9ffa0
> R13: 000055556268f6d0 R14: 431bde82d7b634db R15: 00007fff42f9ffc0
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
> Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8
> 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f>
> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
> RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
> RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
> RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
> R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
> R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
> FS: 000055556268d380(0000) GS:ffff88806b100000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>
>
> ---
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before
> testing.
--
Julian Sun <sunjunchao2870@gmail.com>
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-08-23 5:30 ` Julian Sun
@ 2024-08-23 5:32 ` syzbot
0 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2024-08-23 5:32 UTC (permalink / raw)
To: clm, dsterba, josef, linux-btrfs, linux-kernel, sunjunchao2870,
syzkaller-bugs
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/inode.c
Hunk #1 FAILED at 723.
1 out of 1 hunk FAILED
Tested on:
commit: d30d0e49 Merge tag 'net-6.10-rc3' of git://git.kernel...
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
dashboard link: https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=12ae4b05980000
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-06-07 5:05 ` syzbot
` (2 preceding siblings ...)
2024-08-23 5:30 ` Julian Sun
@ 2024-08-23 5:52 ` Julian Sun
2024-08-23 5:53 ` syzbot
3 siblings, 1 reply; 9+ messages in thread
From: Julian Sun @ 2024-08-23 5:52 UTC (permalink / raw)
To: syzbot, linux-btrfs, linux-kernel, syzkaller-bugs
On Thu, 2024-06-06 at 22:05 -0700, syzbot wrote:
#syz test: upstream d30d0e49da71
diff --git a/fs/inode.c b/fs/inode.c
index 3a41f83a4ba5..011f630777d0 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -723,6 +723,10 @@ void evict_inodes(struct super_block *sb)
continue;
spin_lock(&inode->i_lock);
+ if (atomic_read(&inode->i_count)) {
+ spin_unlock(&inode->i_lock);
+ continue;
+ }
if (inode->i_state & (I_NEW | I_FREEING | I_WILL_FREE))
{
spin_unlock(&inode->i_lock);
continue;
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: d30d0e49da71 Merge tag 'net-6.10-rc3' of
> git://git.kernel...
> git tree: upstream
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=1736820a980000
> kernel config:
> https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils
> for Debian) 2.40
> syz repro:
> https://syzkaller.appspot.com/x/repro.syz?x=11a9aa22980000
> C reproducer:
> https://syzkaller.appspot.com/x/repro.c?x=14c57f16980000
>
> Downloadable assets:
> disk image (non-bootable):
> https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-d30d0e49.raw.xz
> vmlinux:
> https://storage.googleapis.com/syzbot-assets/f1276023ed77/vmlinux-d30d0e49.xz
> kernel image:
> https://storage.googleapis.com/syzbot-assets/a33f372d4fb8/bzImage-d30d0e49.xz
> mounted in repro:
> https://storage.googleapis.com/syzbot-assets/7fc863ff127d/mount_0.gz
>
> IMPORTANT: if you fix the issue, please add the following tag to the
> commit:
> Reported-by: syzbot+67ba3c42bcbb4665d3ad@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> kernel BUG at fs/inode.c:626!
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
> CPU: 1 PID: 5273 Comm: syz-executor331 Not tainted 6.10.0-rc2-
> syzkaller-00222-gd30d0e49da71 #0
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-
> debian-1.16.2-1 04/01/2014
> RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
> Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8
> 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f>
> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
> RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
> RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
> RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
> R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
> R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
> FS: 000055556268d380(0000) GS:ffff88806b100000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> btrfs_evict_inode+0x529/0xe80 fs/btrfs/inode.c:5262
> evict+0x2ed/0x6c0 fs/inode.c:667
> dispose_list+0x117/0x1e0 fs/inode.c:700
> evict_inodes+0x34e/0x450 fs/inode.c:750
> generic_shutdown_super+0xb5/0x3d0 fs/super.c:627
> kill_anon_super+0x3a/0x60 fs/super.c:1226
> btrfs_kill_super+0x3b/0x50 fs/btrfs/super.c:2096
> deactivate_locked_super+0xbe/0x1a0 fs/super.c:473
> deactivate_super+0xde/0x100 fs/super.c:506
> cleanup_mnt+0x222/0x450 fs/namespace.c:1267
> task_work_run+0x14e/0x250 kernel/task_work.c:180
> resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
> exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
> exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
> __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
> syscall_exit_to_user_mode+0x278/0x2a0 kernel/entry/common.c:218
> do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f2ba3059777
> Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66
> 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48>
> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
> RSP: 002b:00007fff42f9ee78 EFLAGS: 00000206 ORIG_RAX:
> 00000000000000a6
> RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f2ba3059777
> RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff42f9ef30
> RBP: 00007fff42f9ef30 R08: 0000000000000000 R09: 0000000000000000
> R10: 00000000ffffffff R11: 0000000000000206 R12: 00007fff42f9ffa0
> R13: 000055556268f6d0 R14: 431bde82d7b634db R15: 00007fff42f9ffc0
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:clear_inode+0x15b/0x190 fs/inode.c:626
> Code: 00 00 00 5b 5d 41 5c c3 cc cc cc cc e8 5e c1 8c ff 90 0f 0b e8
> 56 c1 8c ff 90 0f 0b e8 4e c1 8c ff 90 0f 0b e8 46 c1 8c ff 90 <0f>
> 0b e8 3e c1 8c ff 90 0f 0b e8 e6 92 e8 ff e9 d2 fe ff ff e8 dc
> RSP: 0018:ffffc900036f7ac0 EFLAGS: 00010293
> RAX: 0000000000000000 RBX: ffff888030369e90 RCX: ffffffff82012340
> RDX: ffff888024190000 RSI: ffffffff820123aa RDI: 0000000000000007
> RBP: 0000000000000040 R08: 0000000000000007 R09: 0000000000000000
> R10: 0000000000000040 R11: 0000000000000001 R12: 0000000000000020
> R13: ffff88802f942000 R14: 0000000000000000 R15: ffff888030369e90
> FS: 000055556268d380(0000) GS:ffff88806b100000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000555562697708 CR3: 000000001e888000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>
>
> ---
> If you want syzbot to run the reproducer, reply with:
> #syz test: git://repo/address.git branch-or-commit-hash
> If you attach or paste a git patch, syzbot will apply it before
> testing.
--
Julian Sun <sunjunchao2870@gmail.com>
^ permalink raw reply related [flat|nested] 9+ messages in thread
* Re: [syzbot] [btrfs?] kernel BUG in clear_inode
2024-08-23 5:52 ` Julian Sun
@ 2024-08-23 5:53 ` syzbot
0 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2024-08-23 5:53 UTC (permalink / raw)
To: linux-btrfs, linux-kernel, sunjunchao2870, syzkaller-bugs
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/inode.c
Hunk #1 FAILED at 723.
1 out of 1 hunk FAILED
Tested on:
commit: d30d0e49 Merge tag 'net-6.10-rc3' of git://git.kernel...
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=399230c250e8119c
dashboard link: https://syzkaller.appspot.com/bug?extid=67ba3c42bcbb4665d3ad
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1151ddd5980000
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2024-08-23 5:53 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-05-31 18:56 [syzbot] [btrfs?] kernel BUG in clear_inode syzbot
2024-06-07 5:05 ` syzbot
2024-07-30 14:43 ` David Sterba
2024-08-21 9:42 ` Julian Sun
2024-08-21 10:08 ` syzbot
2024-08-23 5:30 ` Julian Sun
2024-08-23 5:32 ` syzbot
2024-08-23 5:52 ` Julian Sun
2024-08-23 5:53 ` syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).