* WARNING in firmware_fallback_sysfs
@ 2021-03-04 8:20 syzbot
2021-03-25 4:04 ` [syzbot] " syzbot
2023-11-06 17:09 ` [syzbot] syz-test syzbot
0 siblings, 2 replies; 4+ messages in thread
From: syzbot @ 2021-03-04 8:20 UTC (permalink / raw)
To: gregkh, linux-kernel, rafael, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 5695e516 Merge tag 'io_uring-worker.v3-2021-02-25' of git:..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16f34e46d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=90173e86f0624adc
dashboard link: https://syzkaller.appspot.com/bug?extid=95f2e2439b97575ec3c0
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+95f2e2439b97575ec3c0@syzkaller.appspotmail.com
------------[ cut here ]------------
sysfs group 'power' not found for kobject 'ueagle-atm!eagleI.fw'
WARNING: CPU: 1 PID: 32 at fs/sysfs/group.c:279 sysfs_remove_group+0x94/0xa0 fs/sysfs/group.c:279
Modules linked in:
CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted 5.11.0-syzkaller-11646-g5695e5161974 #0
Hardware name: linux,dummy-virt (DT)
Workqueue: events request_firmware_work_func
pstate: 60400009 (nZCv daif +PAN -UAO -TCO BTYPE=--)
pc : sysfs_remove_group+0x94/0xa0 fs/sysfs/group.c:279
lr : sysfs_remove_group+0x94/0xa0 fs/sysfs/group.c:279
sp : ffff800013e83bb0
x29: ffff800013e83bb0 x28: ffff800013a9de40
x27: f5ff00000dff3688 x26: f5ff00000dff3620
x25: f9ff00000b7e40a0 x24: faff00000a690b00
x23: f9ff00000b7e40a0 x22: 0000000000000000
x21: fdff00000de85808 x20: ffff8000124a9818
x19: 0000000000000000 x18: 00000000fffffffd
x17: 0000000000000000 x16: 0000000000000000
x15: 0000000000000020 x14: ffffffffffffffff
x13: 0000000000000e0b x12: ffff800013e83860
x11: ffff800013a0b548 x10: 00000000ffffe000
x9 : ffff800013a0b548 x8 : ffff80001395b548
x7 : ffff800013a0b548 x6 : 0000000000000000
x5 : ffff00007fbd7948 x4 : 0000000000015ff5
x3 : 0000000000000001 x2 : 0000000000000000
x1 : 0000000000000000 x0 : f5ff00000412eac0
Call trace:
sysfs_remove_group+0x94/0xa0 fs/sysfs/group.c:279
dpm_sysfs_remove+0x60/0x70 drivers/base/power/sysfs.c:837
device_del+0xa4/0x384 drivers/base/core.c:3398
fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:543 [inline]
fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:581 [inline]
firmware_fallback_sysfs+0x35c/0x460 drivers/base/firmware_loader/fallback.c:657
_request_firmware+0x4c8/0x6d0 drivers/base/firmware_loader/main.c:831
request_firmware_work_func+0x40/0xa0 drivers/base/firmware_loader/main.c:1077
process_one_work+0x1d8/0x364 kernel/workqueue.c:2275
worker_thread+0x70/0x434 kernel/workqueue.c:2421
kthread+0x174/0x180 kernel/kthread.c:292
ret_from_fork+0x10/0x34 arch/arm64/kernel/entry.S:958
---
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [syzbot] WARNING in firmware_fallback_sysfs
2021-03-04 8:20 WARNING in firmware_fallback_sysfs syzbot
@ 2021-03-25 4:04 ` syzbot
2023-11-06 17:09 ` [syzbot] syz-test syzbot
1 sibling, 0 replies; 4+ messages in thread
From: syzbot @ 2021-03-25 4:04 UTC (permalink / raw)
To: gregkh, linux-kernel, rafael, syzkaller-bugs
syzbot has found a reproducer for the following issue on:
HEAD commit: 20f1b5f9 Add linux-next specific files for 20210324
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1506414ed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=31aa577aa2dca78c
dashboard link: https://syzkaller.appspot.com/bug?extid=95f2e2439b97575ec3c0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e50426d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1388dfe6d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+95f2e2439b97575ec3c0@syzkaller.appspotmail.com
sysfs group 'power' not found for kobject 'ueagle-atm!eagleI.fw'
WARNING: CPU: 1 PID: 36 at fs/sysfs/group.c:279 sysfs_remove_group+0x126/0x170 fs/sysfs/group.c:279
Modules linked in:
CPU: 1 PID: 36 Comm: kworker/1:1 Not tainted 5.12.0-rc4-next-20210324-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events request_firmware_work_func
RIP: 0010:sysfs_remove_group+0x126/0x170 fs/sysfs/group.c:279
Code: 48 89 d9 49 8b 14 24 48 b8 00 00 00 00 00 fc ff df 48 c1 e9 03 80 3c 01 00 75 37 48 8b 33 48 c7 c7 e0 7d 7c 89 e8 9d cc d9 06 <0f> 0b eb 98 e8 f1 23 c9 ff e9 01 ff ff ff 48 89 df e8 e4 23 c9 ff
RSP: 0018:ffffc90000e6faa0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffffff89da8900 RCX: 0000000000000000
RDX: ffff888011e01c80 RSI: ffffffff815c3fd5 RDI: fffff520001cdf46
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff815bd77e R11: 0000000000000000 R12: ffff8880276ac008
R13: ffffffff89da8ea0 R14: ffff8880133e6878 R15: ffff8880133e68c0
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2c3971a0c8 CR3: 000000001cf2a000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
dpm_sysfs_remove+0x97/0xb0 drivers/base/power/sysfs.c:837
device_del+0x20c/0xd40 drivers/base/core.c:3398
fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:543 [inline]
fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:581 [inline]
firmware_fallback_sysfs+0x9ff/0xe20 drivers/base/firmware_loader/fallback.c:657
_request_firmware+0xa80/0xe80 drivers/base/firmware_loader/main.c:833
request_firmware_work_func+0xdd/0x230 drivers/base/firmware_loader/main.c:1079
process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [syzbot] syz-test
2021-03-04 8:20 WARNING in firmware_fallback_sysfs syzbot
2021-03-25 4:04 ` [syzbot] " syzbot
@ 2023-11-06 17:09 ` syzbot
1 sibling, 0 replies; 4+ messages in thread
From: syzbot @ 2023-11-06 17:09 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: syz-test
Author: jose.pekkarinen@foxhound.fi
#syz test:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
5a6a09e97199d6600d31383055f9d43fbbcbe86f
José Pekkarinen.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [syzbot] [block?] memory leak in iov_iter_extract_pages
@ 2023-08-17 1:56 syzbot
2023-11-11 7:14 ` [syzbot] syz-test syzbot
0 siblings, 1 reply; 4+ messages in thread
From: syzbot @ 2023-08-17 1:56 UTC (permalink / raw)
To: axboe, linux-block, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: ae545c3283dc Merge tag 'gpio-fixes-for-v6.5-rc6' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17d1456fa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=2bf8962e4f7984f4
dashboard link: https://syzkaller.appspot.com/bug?extid=cb729843d0f42a5c1a50
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143edef7a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e93037a80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ab6a1e819c1f/disk-ae545c32.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/55f3314970f5/vmlinux-ae545c32.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1a27c3b2a812/bzImage-ae545c32.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+cb729843d0f42a5c1a50@syzkaller.appspotmail.com
Warning: Permanently added '10.128.1.14' (ED25519) to the list of known hosts.
executing program
executing program
executing program
BUG: memory leak
unreferenced object 0xffff888109d2e400 (size 1024):
comm "syz-executor121", pid 5006, jiffies 4294943225 (age 17.760s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81554bbb>] __do_kmalloc_node mm/slab_common.c:984 [inline]
[<ffffffff81554bbb>] __kmalloc_node+0x4b/0x150 mm/slab_common.c:992
[<ffffffff815440f9>] kmalloc_node include/linux/slab.h:602 [inline]
[<ffffffff815440f9>] kvmalloc_node+0x99/0x170 mm/util.c:604
[<ffffffff824c52fe>] kvmalloc include/linux/slab.h:720 [inline]
[<ffffffff824c52fe>] kvmalloc_array include/linux/slab.h:738 [inline]
[<ffffffff824c52fe>] want_pages_array lib/iov_iter.c:985 [inline]
[<ffffffff824c52fe>] iov_iter_extract_user_pages lib/iov_iter.c:1765 [inline]
[<ffffffff824c52fe>] iov_iter_extract_pages+0x1ee/0xa40 lib/iov_iter.c:1831
[<ffffffff824125a7>] bio_map_user_iov+0x167/0x5d0 block/blk-map.c:297
[<ffffffff82412df3>] blk_rq_map_user_iov+0x3e3/0xb30 block/blk-map.c:664
[<ffffffff82413943>] blk_rq_map_user block/blk-map.c:691 [inline]
[<ffffffff82413943>] blk_rq_map_user_io+0x143/0x160 block/blk-map.c:724
[<ffffffff82ca0925>] sg_io+0x285/0x510 drivers/scsi/scsi_ioctl.c:456
[<ffffffff82ca1025>] scsi_cdrom_send_packet+0x1b5/0x480 drivers/scsi/scsi_ioctl.c:820
[<ffffffff82ca13ba>] scsi_ioctl+0xca/0xd30 drivers/scsi/scsi_ioctl.c:903
[<ffffffff82d35964>] sg_ioctl+0x5f4/0x10a0 drivers/scsi/sg.c:1163
[<ffffffff8168e602>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff8168e602>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff8168e602>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff8168e602>] __x64_sys_ioctl+0xf2/0x140 fs/ioctl.c:856
[<ffffffff84ad2bb8>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff84ad2bb8>] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
[<ffffffff84c0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
BUG: memory leak
unreferenced object 0xffff888109d2dc00 (size 1024):
comm "syz-executor121", pid 5007, jiffies 4294943747 (age 12.540s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81554bbb>] __do_kmalloc_node mm/slab_common.c:984 [inline]
[<ffffffff81554bbb>] __kmalloc_node+0x4b/0x150 mm/slab_common.c:992
[<ffffffff815440f9>] kmalloc_node include/linux/slab.h:602 [inline]
[<ffffffff815440f9>] kvmalloc_node+0x99/0x170 mm/util.c:604
[<ffffffff824c52fe>] kvmalloc include/linux/slab.h:720 [inline]
[<ffffffff824c52fe>] kvmalloc_array include/linux/slab.h:738 [inline]
[<ffffffff824c52fe>] want_pages_array lib/iov_iter.c:985 [inline]
[<ffffffff824c52fe>] iov_iter_extract_user_pages lib/iov_iter.c:1765 [inline]
[<ffffffff824c52fe>] iov_iter_extract_pages+0x1ee/0xa40 lib/iov_iter.c:1831
[<ffffffff824125a7>] bio_map_user_iov+0x167/0x5d0 block/blk-map.c:297
[<ffffffff82412df3>] blk_rq_map_user_iov+0x3e3/0xb30 block/blk-map.c:664
[<ffffffff82413943>] blk_rq_map_user block/blk-map.c:691 [inline]
[<ffffffff82413943>] blk_rq_map_user_io+0x143/0x160 block/blk-map.c:724
[<ffffffff82ca0925>] sg_io+0x285/0x510 drivers/scsi/scsi_ioctl.c:456
[<ffffffff82ca1025>] scsi_cdrom_send_packet+0x1b5/0x480 drivers/scsi/scsi_ioctl.c:820
[<ffffffff82ca13ba>] scsi_ioctl+0xca/0xd30 drivers/scsi/scsi_ioctl.c:903
[<ffffffff82d35964>] sg_ioctl+0x5f4/0x10a0 drivers/scsi/sg.c:1163
[<ffffffff8168e602>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff8168e602>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff8168e602>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff8168e602>] __x64_sys_ioctl+0xf2/0x140 fs/ioctl.c:856
[<ffffffff84ad2bb8>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff84ad2bb8>] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
[<ffffffff84c0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
BUG: memory leak
unreferenced object 0xffff888109d2d800 (size 1024):
comm "syz-executor121", pid 5010, jiffies 4294944269 (age 7.320s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<ffffffff81554bbb>] __do_kmalloc_node mm/slab_common.c:984 [inline]
[<ffffffff81554bbb>] __kmalloc_node+0x4b/0x150 mm/slab_common.c:992
[<ffffffff815440f9>] kmalloc_node include/linux/slab.h:602 [inline]
[<ffffffff815440f9>] kvmalloc_node+0x99/0x170 mm/util.c:604
[<ffffffff824c52fe>] kvmalloc include/linux/slab.h:720 [inline]
[<ffffffff824c52fe>] kvmalloc_array include/linux/slab.h:738 [inline]
[<ffffffff824c52fe>] want_pages_array lib/iov_iter.c:985 [inline]
[<ffffffff824c52fe>] iov_iter_extract_user_pages lib/iov_iter.c:1765 [inline]
[<ffffffff824c52fe>] iov_iter_extract_pages+0x1ee/0xa40 lib/iov_iter.c:1831
[<ffffffff824125a7>] bio_map_user_iov+0x167/0x5d0 block/blk-map.c:297
[<ffffffff82412df3>] blk_rq_map_user_iov+0x3e3/0xb30 block/blk-map.c:664
[<ffffffff82413943>] blk_rq_map_user block/blk-map.c:691 [inline]
[<ffffffff82413943>] blk_rq_map_user_io+0x143/0x160 block/blk-map.c:724
[<ffffffff82ca0925>] sg_io+0x285/0x510 drivers/scsi/scsi_ioctl.c:456
[<ffffffff82ca1025>] scsi_cdrom_send_packet+0x1b5/0x480 drivers/scsi/scsi_ioctl.c:820
[<ffffffff82ca13ba>] scsi_ioctl+0xca/0xd30 drivers/scsi/scsi_ioctl.c:903
[<ffffffff82d35964>] sg_ioctl+0x5f4/0x10a0 drivers/scsi/sg.c:1163
[<ffffffff8168e602>] vfs_ioctl fs/ioctl.c:51 [inline]
[<ffffffff8168e602>] __do_sys_ioctl fs/ioctl.c:870 [inline]
[<ffffffff8168e602>] __se_sys_ioctl fs/ioctl.c:856 [inline]
[<ffffffff8168e602>] __x64_sys_ioctl+0xf2/0x140 fs/ioctl.c:856
[<ffffffff84ad2bb8>] do_syscall_x64 arch/x86/entry/common.c:50 [inline]
[<ffffffff84ad2bb8>] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
[<ffffffff84c0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
---
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 bug is already fixed, 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 bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-11-11 7:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-03-04 8:20 WARNING in firmware_fallback_sysfs syzbot
2021-03-25 4:04 ` [syzbot] " syzbot
2023-11-06 17:09 ` [syzbot] syz-test syzbot
-- strict thread matches above, loose matches on Subject: below --
2023-08-17 1:56 [syzbot] [block?] memory leak in iov_iter_extract_pages syzbot
2023-11-11 7:14 ` [syzbot] syz-test syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox