mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+79a6b3f7a8df01f58774@syzkaller.appspotmail.com>
To: Frank.Li@kernel.org, dave.jiang@intel.com,
	dmaengine@vger.kernel.org,  frank.li@kernel.org,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com,
	vkoul@kernel.org
Subject: Re: [syzbot] [dmaengine?] BUG: unable to handle kernel paging request in ioat_pci_probe
Date: Sat, 21 Nov 2026 07:25:47 -0800	[thread overview]
Message-ID: <6b01b7fb.44b41460.34b83f.000f.GAE@google.com> (raw)
In-Reply-To: <6a891a2c.91706f20.16b6e3.02b1.GAE@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    909ef7a9a30f Add linux-next specific files for 20261120
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=13ca7cd5580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=15db63a14ba195ac
dashboard link: https://syzkaller.appspot.com/bug?extid=79a6b3f7a8df01f58774
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10a07185580000

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

BUG: unable to handle page fault for address: 000000000001c008
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 8000000074684067 P4D 8000000074684067 PUD 0 
Oops: Oops: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 6362 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
RIP: 0010:readb arch/x86/include/asm/io.h:57 [inline]
RIP: 0010:ioat_pci_probe+0xad/0x410 drivers/dma/ioat/init.c:1365
Code: 48 85 c0 74 4c 49 89 c7 48 b8 00 00 00 00 00 fc ff df 4c 89 fb 48 c1 eb 03 80 3c 03 00 74 08 4c 89 ff e8 06 55 c3 fc 49 8b 07 <44> 8a 60 08 41 0f b6 ec bf 30 00 00 00 89 ee e8 2f 13 43 fc 41 80
RSP: 0018:ffffc900034578f8 EFLAGS: 00010246
RAX: 000000000001c000 RBX: 1ffff110056d8ae7 RCX: ffff88801c9d5dc0
RDX: 0000000000000000 RSI: ffffffff8ea2b415 RDI: 00000000ffffffff
RBP: ffffc90003457b20 R08: ffffffff91e1e4bf R09: 1ffffffff23c3c97
R10: dffffc0000000000 R11: fffffbfff23c3c98 R12: 1ffff110045d3c10
R13: 0000000000000000 R14: ffff888022e9e000 R15: ffff88802b6c5738
FS:  00007f687f7dd6c0(0000) GS:ffff8881231fd000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000001c008 CR3: 000000007f156000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 local_pci_probe drivers/pci/pci-driver.c:355 [inline]
 pci_call_probe drivers/pci/pci-driver.c:417 [inline]
 __pci_device_probe drivers/pci/pci-driver.c:479 [inline]
 pci_device_probe+0x48e/0xd10 drivers/pci/pci-driver.c:513
 call_driver_probe drivers/base/dd.c:-1 [inline]
 really_probe+0x254/0xae0 drivers/base/dd.c:707
 __driver_probe_device+0x1e8/0x360 drivers/base/dd.c:869
 device_driver_attach+0xe4/0x1f0 drivers/base/dd.c:1211
 bind_store+0x1d0/0x220 drivers/base/bus.c:267
 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345
 new_sync_write fs/read_write.c:580 [inline]
 vfs_write+0x612/0xba0 fs/read_write.c:672
 ksys_write+0x150/0x270 fs/read_write.c:1021
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x171/0x540 arch/x86/entry/syscall_64.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x00007f688019e0d9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f687f7dd028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f6880426090 RCX: 00007f688019e0d9
RDX: 000000000000000d RSI: 0000200000000600 RDI: 0000000000000005
RBP: 00007f6880235024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6880426128 R14: 00007f6880426090 R15: 00007ffcb8a3f2d8
 </TASK>
Modules linked in:
CR2: 000000000001c008
---[ end trace 0000000000000000 ]---
RIP: 0010:readb arch/x86/include/asm/io.h:57 [inline]
RIP: 0010:ioat_pci_probe+0xad/0x410 drivers/dma/ioat/init.c:1365
Code: 48 85 c0 74 4c 49 89 c7 48 b8 00 00 00 00 00 fc ff df 4c 89 fb 48 c1 eb 03 80 3c 03 00 74 08 4c 89 ff e8 06 55 c3 fc 49 8b 07 <44> 8a 60 08 41 0f b6 ec bf 30 00 00 00 89 ee e8 2f 13 43 fc 41 80
RSP: 0018:ffffc900034578f8 EFLAGS: 00010246
RAX: 000000000001c000 RBX: 1ffff110056d8ae7 RCX: ffff88801c9d5dc0
RDX: 0000000000000000 RSI: ffffffff8ea2b415 RDI: 00000000ffffffff
RBP: ffffc90003457b20 R08: ffffffff91e1e4bf R09: 1ffffffff23c3c97
R10: dffffc0000000000 R11: fffffbfff23c3c98 R12: 1ffff110045d3c10
R13: 0000000000000000 R14: ffff888022e9e000 R15: ffff88802b6c5738
FS:  00007f687f7dd6c0(0000) GS:ffff8881231fd000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000001c008 CR3: 000000007f156000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
   0:	48 85 c0             	test   %rax,%rax
   3:	74 4c                	je     0x51
   5:	49 89 c7             	mov    %rax,%r15
   8:	48 b8 00 00 00 00 00 	movabs $0xdffffc0000000000,%rax
   f:	fc ff df
  12:	4c 89 fb             	mov    %r15,%rbx
  15:	48 c1 eb 03          	shr    $0x3,%rbx
  19:	80 3c 03 00          	cmpb   $0x0,(%rbx,%rax,1)
  1d:	74 08                	je     0x27
  1f:	4c 89 ff             	mov    %r15,%rdi
  22:	e8 06 55 c3 fc       	call   0xfcc3552d
  27:	49 8b 07             	mov    (%r15),%rax
* 2a:	44 8a 60 08          	mov    0x8(%rax),%r12b <-- trapping instruction
  2e:	41 0f b6 ec          	movzbl %r12b,%ebp
  32:	bf 30 00 00 00       	mov    $0x30,%edi
  37:	89 ee                	mov    %ebp,%esi
  39:	e8 2f 13 43 fc       	call   0xfc43136d
  3e:	41                   	rex.B
  3f:	80                   	.byte 0x80

      parent reply	other threads:[~2026-11-21 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22  3:40 syzbot
2026-08-24 16:02 ` Dave Jiang
2026-11-21 15:25 ` syzbot [this message]

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=6b01b7fb.44b41460.34b83f.000f.GAE@google.com \
    --to=syzbot+79a6b3f7a8df01f58774@syzkaller.appspotmail.com \
    --cc=Frank.Li@kernel.org \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vkoul@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®