All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+49b1021becba70c1f3f6@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	 linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
	 peterz@infradead.org, syzkaller-bugs@googlegroups.com,
	tglx@kernel.org,  x86@kernel.org
Subject: [syzbot] [kernel?] WARNING in __ioremap_caller
Date: Sun, 22 Feb 2026 03:33:32 -0800	[thread overview]
Message-ID: <699ae98c.050a0220.340abe.0d31.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    2961f841b025 Merge tag 'turbostat-2026.02.14' of git://git..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17674594580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6259cfbe2d15cac4
dashboard link: https://syzkaller.appspot.com/bug?extid=49b1021becba70c1f3f6
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4db266f4e980/disk-2961f841.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9ec134f45048/vmlinux-2961f841.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5ba4f405d712/bzImage-2961f841.xz

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

ioremap: invalid physical address a729678abbd17117
------------[ cut here ]------------
1
WARNING: arch/x86/mm/ioremap.c:206 at __ioremap_caller.isra.0.cold+0x59/0xa4 arch/x86/mm/ioremap.c:206, CPU#0: syz.1.4191/26162
Modules linked in:
CPU: 0 UID: 0 PID: 26162 Comm: syz.1.4191 Tainted: G     U       L      syzkaller #0 PREEMPT(full) 
Tainted: [U]=USER, [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__ioremap_caller.isra.0.cold+0x59/0xa4 arch/x86/mm/ioremap.c:206
Code: 48 8b 34 24 48 c7 c7 e0 fc ab 8b e8 30 1d 01 00 e9 61 c2 97 00 e8 76 ca e6 00 4c 89 ee 48 c7 c7 40 fb ab 8b e8 17 1d 01 00 90 <0f> 0b 90 e9 41 c2 97 00 e8 59 ca e6 00 41 0f b6 d7 4c 89 ee 48 c7
RSP: 0018:ffffc90004d1f718 EFLAGS: 00010286
RAX: 0000000000000032 RBX: 1ffff920009a3ee7 RCX: 0000000000000000
RDX: 0000000000000032 RSI: ffffffff81e6f929 RDI: fffff520009a3ed4
RBP: 0000000000000040 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000038c68 R12: a729678abbd17156
R13: a729678abbd17117 R14: 0000000000000000 R15: 0000000000029ca5
FS:  00007fc5be1016c0(0000) GS:ffff888124351000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32306ff8 CR3: 00000000831e0000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 ioremap_cache arch/x86/mm/ioremap.c:436 [inline]
 arch_memremap_wb+0x23/0x40 arch/x86/mm/ioremap.c:508
 memremap+0x1cb/0x7d0 kernel/iomem.c:95
 pcibios_device_add+0x101/0x600 arch/x86/pci/common.c:652
 pci_device_add+0xd4f/0x1810 drivers/pci/probe.c:2761
 pci_scan_single_device drivers/pci/probe.c:2793 [inline]
 pci_scan_single_device+0x1d0/0x240 drivers/pci/probe.c:2779
 pci_scan_slot+0x1c9/0x7c0 drivers/pci/probe.c:2876
 pci_scan_child_bus_extend+0x6b/0x7b0 drivers/pci/probe.c:3095
 pci_scan_child_bus drivers/pci/probe.c:3208 [inline]
 pci_rescan_bus+0x18/0x40 drivers/pci/probe.c:3499
 rescan_store+0xfb/0x130 drivers/pci/pci-sysfs.c:472
 bus_attr_store+0x74/0xb0 drivers/base/bus.c:172
 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:142
 kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:352
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x6ac/0x1070 fs/read_write.c:688
 ksys_write+0x12a/0x250 fs/read_write.c:740
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc5bd19c629
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:00007fc5be101028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc5bd415fa0 RCX: 00007fc5bd19c629
RDX: 0000000000000001 RSI: 0000200000000200 RDI: 0000000000000003
RBP: 00007fc5bd232b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc5bd416038 R14: 00007fc5bd415fa0 R15: 00007ffc328057a8
 </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

                 reply	other threads:[~2026-02-22 11:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=699ae98c.050a0220.340abe.0d31.GAE@google.com \
    --to=syzbot+49b1021becba70c1f3f6@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@kernel.org \
    --cc=x86@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 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.