[syzbot] [fuse?] WARNING in fuse_request_end (2)

[syzbot] [fuse?] WARNING in fuse_request_end (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    4d0326b60bb7 Add linux-next specific files for 20240924
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=119dc99f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=441f6022e7a2db73
dashboard link: https://syzkaller.appspot.com/bug?extid=554c4743d0f2d52d990d
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5461991c7c3f/disk-4d0326b6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2d44fd40ed13/vmlinux-4d0326b6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25eeeb66df29/bzImage-4d0326b6.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5282 at fs/fuse/dev.c:372 fuse_request_end+0x875/0xad0 fs/fuse/dev.c:372
Modules linked in:
CPU: 1 UID: 0 PID: 5282 Comm: kworker/1:6 Not tainted 6.11.0-next-20240924-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Workqueue: events close_work
RIP: 0010:fuse_request_end+0x875/0xad0 fs/fuse/dev.c:372
Code: 89 ef e8 4e ab e9 fe 48 8b 45 00 48 39 e8 74 0a e8 80 e9 7f fe e9 28 fc ff ff e8 76 e9 7f fe e9 79 fc ff ff e8 6c e9 7f fe 90 <0f> 0b 90 e9 a9 fa ff ff e8 5e e9 7f fe 90 0f 0b 90 e9 dd fa ff ff
RSP: 0018:ffffc90004297790 EFLAGS: 00010293
RAX: ffffffff8314f984 RBX: 000000000000028b RCX: ffff88806288da00
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 0000000000000000
RBP: 0000000000000080 R08: ffffffff8314f428 R09: 1ffff110062c1738
R10: dffffc0000000000 R11: ffffed10062c1739 R12: ffff88803160b990
R13: 1ffff110062c1738 R14: ffff88803160b9c0 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f570e302d58 CR3: 000000002d052000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __fuse_request_send fs/fuse/dev.c:475 [inline]
 __fuse_simple_request+0xaad/0x1840 fs/fuse/dev.c:571
 fuse_simple_request fs/fuse/fuse_i.h:1156 [inline]
 fuse_flush+0x69d/0x950 fs/fuse/file.c:542
 close_work+0x89/0xb0 kernel/acct.c:206
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>


---
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

Re: [syzbot] [fuse?] WARNING in fuse_request_end (2)

[Joanne Koong]

On Sat, Sep 28, 2024 at 1:06 AM syzbot
<syzbot+554c4743d0f2d52d990d@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:    4d0326b60bb7 Add linux-next specific files for 20240924
> git tree:       linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=119dc99f980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=441f6022e7a2db73
> dashboard link: https://syzkaller.appspot.com/bug?extid=554c4743d0f2d52d990d
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/5461991c7c3f/disk-4d0326b6.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/2d44fd40ed13/vmlinux-4d0326b6.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/25eeeb66df29/bzImage-4d0326b6.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+554c4743d0f2d52d990d@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 5282 at fs/fuse/dev.c:372 fuse_request_end+0x875/0xad0 fs/fuse/dev.c:372
> Modules linked in:
> CPU: 1 UID: 0 PID: 5282 Comm: kworker/1:6 Not tainted 6.11.0-next-20240924-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
> Workqueue: events close_work
> RIP: 0010:fuse_request_end+0x875/0xad0 fs/fuse/dev.c:372
> Code: 89 ef e8 4e ab e9 fe 48 8b 45 00 48 39 e8 74 0a e8 80 e9 7f fe e9 28 fc ff ff e8 76 e9 7f fe e9 79 fc ff ff e8 6c e9 7f fe 90 <0f> 0b 90 e9 a9 fa ff ff e8 5e e9 7f fe 90 0f 0b 90 e9 dd fa ff ff
> RSP: 0018:ffffc90004297790 EFLAGS: 00010293
> RAX: ffffffff8314f984 RBX: 000000000000028b RCX: ffff88806288da00
> RDX: 0000000000000000 RSI: 0000000000000080 RDI: 0000000000000000
> RBP: 0000000000000080 R08: ffffffff8314f428 R09: 1ffff110062c1738
> R10: dffffc0000000000 R11: ffffed10062c1739 R12: ffff88803160b990
> R13: 1ffff110062c1738 R14: ffff88803160b9c0 R15: dffffc0000000000
> FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f570e302d58 CR3: 000000002d052000 CR4: 00000000003526f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>  <TASK>
>  __fuse_request_send fs/fuse/dev.c:475 [inline]
>  __fuse_simple_request+0xaad/0x1840 fs/fuse/dev.c:571
>  fuse_simple_request fs/fuse/fuse_i.h:1156 [inline]
>  fuse_flush+0x69d/0x950 fs/fuse/file.c:542
>  close_work+0x89/0xb0 kernel/acct.c:206
>  process_one_work kernel/workqueue.c:3229 [inline]
>  process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
>  worker_thread+0x870/0xd30 kernel/workqueue.c:3391
>  kthread+0x2f0/0x390 kernel/kthread.c:389
>  ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
>  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
>  </TASK>
>
>

#syz fix: fuse: clear FR_PENDING if abort is detected when sending request

This has already been fixed by commit fcd2d9e1fdcd "fuse: clear
FR_PENDING if abort is detected when sending request"


> ---
> 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
>