All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
	perex@perex.cz,  syzkaller-bugs@googlegroups.com, tiwai@suse.com
Subject: [syzbot] [sound?] kernel BUG in filemap_fault (2)
Date: Mon, 16 Jun 2025 04:13:29 -0700	[thread overview]
Message-ID: <684ffc59.a00a0220.279073.0037.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    488ef3560196 KEYS: Invert FINAL_PUT bit
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1503a10c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=162faeb2d1eaefb4
dashboard link: https://syzkaller.appspot.com/bug?extid=263f159eb37a1c4c67a4
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/10b92ce8eca6/disk-488ef356.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4d4223a305b2/vmlinux-488ef356.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b4a8f82f3ac9/bzImage-488ef356.xz

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

 lookup_one_qstr_excl fs/namei.c:1711 [inline]
 do_renameat2+0x470/0xc50 fs/namei.c:5234
 __do_sys_rename fs/namei.c:5324 [inline]
 __se_sys_rename fs/namei.c:5322 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5322
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
------------[ cut here ]------------
kernel BUG at mm/filemap.c:3442!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 7049 Comm: syz.2.293 Not tainted 6.16.0-rc1-syzkaller-00005-g488ef3560196 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:filemap_fault+0x117d/0x1200 mm/filemap.c:3442
Code: 38 c1 0f 8c 8e fc ff ff 4c 89 e7 e8 ad 64 29 00 e9 81 fc ff ff e8 23 18 c8 ff 48 89 df 48 c7 c6 20 30 94 8b e8 c4 a7 0d 00 90 <0f> 0b e8 0c 18 c8 ff 48 8b 3c 24 48 c7 c6 a0 36 94 8b e8 ac a7 0d
RSP: 0018:ffffc90004b073c0 EFLAGS: 00010246
RAX: f04d382b8d45cd00 RBX: ffffea0001dae580 RCX: f04d382b8d45cd00
RDX: 0000000000000000 RSI: ffffffff8db594ef RDI: ffff888027438000
RBP: ffffc90004b074f8 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bfa9ec R12: dffffc0000000000
R13: 1ffffd40003b5cb1 R14: ffffea0001dae598 R15: ffffea0001dae588
FS:  00007f5736abb6c0(0000) GS:ffff888125c86000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000069e2 CR3: 0000000028984000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __do_fault+0x135/0x390 mm/memory.c:5189
 do_read_fault mm/memory.c:5610 [inline]
 do_fault mm/memory.c:5744 [inline]
 do_pte_missing mm/memory.c:4251 [inline]
 handle_pte_fault mm/memory.c:6089 [inline]
 __handle_mm_fault+0x37ed/0x5620 mm/memory.c:6232
 handle_mm_fault+0x2d5/0x7f0 mm/memory.c:6401
 do_user_addr_fault+0x764/0x1390 arch/x86/mm/fault.c:1387
 handle_page_fault arch/x86/mm/fault.c:1476 [inline]
 exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623
RIP: 0010:rep_movs_alternative+0xf/0x90 arch/x86/lib/copy_user_64.S:46
Code: c4 10 c3 cc cc cc cc cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 48 83 f9 40 73 44 83 f9 08 73 25 85 c9 74 0f <8a> 06 88 07 48 ff c7 48 ff c6 48 ff c9 75 f1 e9 fd f6 03 00 66 2e
RSP: 0018:ffffc90004b07978 EFLAGS: 00050202
RAX: 00007ffffffff001 RBX: 0000000000000001 RCX: 0000000000000001
RDX: 0000000000000001 RSI: 00002000000069e2 RDI: ffff8880297ba722
RBP: 00000000000088de R08: ffff8880297ba722 R09: 1ffff110052f74e4
R10: dffffc0000000000 R11: ffffed10052f74e5 R12: 0000000000000000
R13: 0000000000000001 R14: ffff8880297ba722 R15: 00002000000069e2
 copy_user_generic arch/x86/include/asm/uaccess_64.h:126 [inline]
 raw_copy_from_user arch/x86/include/asm/uaccess_64.h:141 [inline]
 _inline_copy_from_user include/linux/uaccess.h:178 [inline]
 _copy_from_user+0x7a/0xb0 lib/usercopy.c:18
 copy_from_user include/linux/uaccess.h:212 [inline]
 snd_rawmidi_kernel_write1+0x3ab/0x650 sound/core/rawmidi.c:1560
 snd_rawmidi_write+0x5ad/0xbd0 sound/core/rawmidi.c:1629
 do_loop_readv_writev fs/read_write.c:850 [inline]
 vfs_writev+0x4b3/0x960 fs/read_write.c:1059
 do_writev+0x14d/0x2d0 fs/read_write.c:1103
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5735b8e929
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f5736abb038 EFLAGS: 00000246 ORIG_RAX: 0000000000000014
RAX: ffffffffffffffda RBX: 00007f5735db5fa0 RCX: 00007f5735b8e929
RDX: 0000000000000002 RSI: 0000200000000840 RDI: 000000000000000a
RBP: 00007f5735c10b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f5735db5fa0 R15: 00007ffe2d0cdd08
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:filemap_fault+0x117d/0x1200 mm/filemap.c:3442
Code: 38 c1 0f 8c 8e fc ff ff 4c 89 e7 e8 ad 64 29 00 e9 81 fc ff ff e8 23 18 c8 ff 48 89 df 48 c7 c6 20 30 94 8b e8 c4 a7 0d 00 90 <0f> 0b e8 0c 18 c8 ff 48 8b 3c 24 48 c7 c6 a0 36 94 8b e8 ac a7 0d
RSP: 0018:ffffc90004b073c0 EFLAGS: 00010246
RAX: f04d382b8d45cd00 RBX: ffffea0001dae580 RCX: f04d382b8d45cd00
RDX: 0000000000000000 RSI: ffffffff8db594ef RDI: ffff888027438000
RBP: ffffc90004b074f8 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bfa9ec R12: dffffc0000000000
R13: 1ffffd40003b5cb1 R14: ffffea0001dae598 R15: ffffea0001dae588
FS:  00007f5736abb6c0(0000) GS:ffff888125c86000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00002000000069e2 CR3: 0000000028984000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
   0:	10 c3                	adc    %al,%bl
   2:	cc                   	int3
   3:	cc                   	int3
   4:	cc                   	int3
   5:	cc                   	int3
   6:	cc                   	int3
   7:	cc                   	int3
   8:	cc                   	int3
   9:	cc                   	int3
   a:	90                   	nop
   b:	90                   	nop
   c:	90                   	nop
   d:	90                   	nop
   e:	90                   	nop
   f:	90                   	nop
  10:	90                   	nop
  11:	90                   	nop
  12:	90                   	nop
  13:	90                   	nop
  14:	90                   	nop
  15:	90                   	nop
  16:	90                   	nop
  17:	90                   	nop
  18:	90                   	nop
  19:	90                   	nop
  1a:	48 83 f9 40          	cmp    $0x40,%rcx
  1e:	73 44                	jae    0x64
  20:	83 f9 08             	cmp    $0x8,%ecx
  23:	73 25                	jae    0x4a
  25:	85 c9                	test   %ecx,%ecx
  27:	74 0f                	je     0x38
* 29:	8a 06                	mov    (%rsi),%al <-- trapping instruction
  2b:	88 07                	mov    %al,(%rdi)
  2d:	48 ff c7             	inc    %rdi
  30:	48 ff c6             	inc    %rsi
  33:	48 ff c9             	dec    %rcx
  36:	75 f1                	jne    0x29
  38:	e9 fd f6 03 00       	jmp    0x3f73a
  3d:	66                   	data16
  3e:	2e                   	cs


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

             reply	other threads:[~2025-06-16 11:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16 11:13 syzbot [this message]
2025-07-03 16:43 ` [syzbot] [net?] kernel BUG in filemap_fault (2) syzbot
2025-07-04  2:20   ` Hillf Danton
2025-07-04  3:00     ` syzbot
2025-09-14 10:51 ` [syzbot] [sound?] " syzbot
2025-09-16 12:50   ` Ryan Roberts
2025-09-16 13:05     ` Jan Kara
2025-09-17  7:57       ` David Hildenbrand
2025-09-17  8:35         ` Jan Kara
2025-09-17  9:04           ` David Hildenbrand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=684ffc59.a00a0220.279073.0037.GAE@google.com \
    --to=syzbot+263f159eb37a1c4c67a4@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.