The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: syzbot <syzbot+901ca72278dfd89daf58@syzkaller.appspotmail.com>
To: dmantipov@yandex.ru, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] BUG: unable to handle kernel paging request in nhi_probe
Date: Thu, 06 Aug 2026 21:39:01 -0700	[thread overview]
Message-ID: <6a756165.9c11d2ce.289b96.00a4.GAE@google.com> (raw)
In-Reply-To: <977109ec-5dd1-4e10-b911-e8bf8a1ef398@yandex.ru>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel BUG in nhi_probe

------------[ cut here ]------------
kernel BUG at drivers/thunderbolt/nhi.c:1200!
Internal error: Oops - BUG: 00000000f2000800 [#1]  SMP
Modules linked in:
CPU: 0 UID: 0 PID: 5347 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026
pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
pc : nhi_probe+0x69c/0x7ac drivers/thunderbolt/nhi.c:1200
lr : nhi_probe+0x69c/0x7ac drivers/thunderbolt/nhi.c:1200
sp : ffff8000944a75b0
x29: ffff8000944a75c0 x28: ffff0000d0ef78c0 x27: 1fffe0001a1def18
x26: 1fffe0001a1def18 x25: 1fffe0001a1def19 x24: 1fffe000185620b7
x23: dfff800000000000 x22: 0000010000003fff x21: 0000000000004000
x20: ffff0000d0ef7880 x19: ffff0000c2b100d0 x18: 00000000ffffffff
x17: ffff80008a772000 x16: 0000000000000005 x15: ffff80008a2fbda0
x14: ffff80008a571e28 x13: 0000000000000001 x12: 0000000000000000
x11: ffff80008a571e28 x10: 0000000000000001 x9 : 0000000000000000
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000008 x3 : ffff800084a59138
x2 : 0000000000004000 x1 : ffff0000c8943a80 x0 : 0000000000000000
Call trace:
 nhi_probe+0x69c/0x7ac drivers/thunderbolt/nhi.c:1200 (P)
 nhi_pci_probe+0x418/0x4e4 drivers/thunderbolt/pci.c:479
 local_pci_probe+0xc8/0x158 drivers/pci/pci-driver.c:332
 pci_call_probe drivers/pci/pci-driver.c:394 [inline]
 __pci_device_probe drivers/pci/pci-driver.c:455 [inline]
 pci_device_probe+0x460/0x8d4 drivers/pci/pci-driver.c:489
 call_driver_probe drivers/base/dd.c:-1 [inline]
 really_probe+0x29c/0x800 drivers/base/dd.c:706
 __driver_probe_device+0x1e0/0x350 drivers/base/dd.c:868
 device_driver_attach+0x58/0xac drivers/base/dd.c:1203
 bind_store+0xf4/0x14c drivers/base/bus.c:267
 drv_attr_store+0x80/0xa4 drivers/base/bus.c:125
 sysfs_kf_write+0xe0/0x108 fs/sysfs/file.c:145
 kernfs_fop_write_iter+0x260/0x3b8 fs/kernfs/file.c:345
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x51c/0xa0c fs/read_write.c:687
 ksys_write+0x12c/0x228 fs/read_write.c:739
 __do_sys_write fs/read_write.c:750 [inline]
 __se_sys_write fs/read_write.c:747 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:747
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x64/0x260 arch/arm64/kernel/entry-common.c:736
 el0t_64_sync_handler+0x48/0x148 arch/arm64/kernel/entry-common.c:755
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:594
Code: 17ffff8d 96eff548 d4210000 96eff546 (d4210000) 
---[ end trace 0000000000000000 ]---


Tested on:

commit:         0d839570 Merge tag 'soc-fixes-7.2-2' of git://git.kern..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1224d7b9580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=ecdef466b08b9772
dashboard link: https://syzkaller.appspot.com/bug?extid=901ca72278dfd89daf58
compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=141777b9580000


       reply	other threads:[~2026-08-07  4:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <977109ec-5dd1-4e10-b911-e8bf8a1ef398@yandex.ru>
2026-08-07  4:39 ` syzbot [this message]
2026-08-06  0:01 [syzbot] [usb?] BUG: unable to handle kernel paging request in nhi_probe syzbot

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=6a756165.9c11d2ce.289b96.00a4.GAE@google.com \
    --to=syzbot+901ca72278dfd89daf58@syzkaller.appspotmail.com \
    --cc=dmantipov@yandex.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox