[syzbot] [kernel?] WARNING in iounmap

[syzbot] [kernel?] WARNING in iounmap

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    704340f1cd0d Merge tag 'x86_urgent_for_7.3-rc4' of git://g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13727a99580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=ca1ef9e2e234b8d3599b
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=110f305e580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=118f88c9580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-704340f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e02afc1c5927/vmlinux-704340f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/09cb4a8b3309/bzImage-704340f1.xz

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

e1000 0000:00:01.0 (unnamed net_device) (uninitialized): Unknown MAC Type
------------[ cut here ]------------
!is_ioremap_addr((void __force *)addr)
WARNING: arch/x86/mm/ioremap.c:460 at iounmap+0x64/0x240 arch/x86/mm/ioremap.c:460, CPU#2: syz.0.17/5914
Modules linked in:
CPU: 2 UID: 0 PID: 5914 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:iounmap+0x64/0x240 arch/x86/mm/ioremap.c:460
Code: df 48 89 ee e8 fd 3c 51 00 48 39 eb 72 16 e8 13 43 51 00 eb 28 cc cc cc 49 bc 00 00 00 00 00 00 32 00 eb 23 e8 fd 42 51 00 90 <0f> 0b 90 e8 f4 42 51 00 5b 5d 41 5c 41 5d c3 cc cc cc cc 49 bc 00
RSP: 0018:ffffc90003ebf7d0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88802403cb00 RSI: ffffffff81bada13 RDI: ffff88802403cb00
RBP: ffffc90000000000 R08: 0000000000000006 R09: 0000000000000000
R10: ffffc90000000000 R11: 0000000000000001 R12: ffff888057315430
R13: ffff88802322a0d0 R14: ffff88802322a03e R15: ffff888057314000
FS:  0000555593d27500(0000) GS:ffff8880d5d59000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000002dbb65fc090 CR3: 0000000036b28000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 e1000_probe+0x1400/0x2cf0 drivers/net/ethernet/intel/e1000/e1000_main.c:1230
 local_pci_probe+0xdd/0x1b0 drivers/pci/pci-driver.c:354
 pci_call_probe+0x176/0x800 drivers/pci/pci-driver.c:416
 __pci_device_probe drivers/pci/pci-driver.c:478 [inline]
 pci_device_probe+0x25b/0x400 drivers/pci/pci-driver.c:512
 call_driver_probe drivers/base/dd.c:628 [inline]
 really_probe+0x241/0xa60 drivers/base/dd.c:706
 __driver_probe_device+0x210/0x460 drivers/base/dd.c:868
 device_driver_attach+0xd1/0x220 drivers/base/dd.c:1203
 bind_store+0xf4/0x190 drivers/base/bus.c:267
 drv_attr_store+0x74/0xb0 drivers/base/bus.c:125
 sysfs_kf_write+0xf2/0x150 fs/sysfs/file.c:145
 kernfs_fop_write_iter+0x3e0/0x5f0 fs/kernfs/file.c:345
 new_sync_write fs/read_write.c:595 [inline]
 vfs_write+0x6af/0x1050 fs/read_write.c:687
 ksys_write+0x12a/0x250 fs/read_write.c:739
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f534839e159
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:00007ffc4dfb30e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f5348625fa0 RCX: 00007f534839e159
RDX: 000000000000000d RSI: 0000200000000800 RDI: 0000000000000007
RBP: 00007f534843503b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5348625fac R14: 00007f5348625fa0 R15: 00007f5348625fa0
 </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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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