[v5.15] WARNING: proc registration bug in bcm_connect
1 view
Skip to first unread message
syzbot
Jan 14, 2024, 6:26:20 AMJan 14
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 26c690eff0a5 Linux 5.15.146
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15df1683e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab948f7b303e76f8
dashboard link: https://syzkaller.appspot.com/bug?extid=e810231fb4eca8a972fd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/33e6f3a42ce6/disk-26c690ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0224f0ff4ede/vmlinux-26c690ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/822737ca97e0/Image-26c690ef.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e81023...@syzkaller.appspotmail.com
------------[ cut here ]------------
proc_dir_entry 'can-bcm/91548' already registered
WARNING: CPU: 1 PID: 23441 at fs/proc/generic.c:377 proc_register+0x2e8/0x464 fs/proc/generic.c:378
Modules linked in:
CPU: 1 PID: 23441 Comm: syz-executor.4 Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : proc_register+0x2e8/0x464 fs/proc/generic.c:378
lr : proc_register+0x2e0/0x464 fs/proc/generic.c:376
sp : ffff800021497a20
x29: ffff800021497a40 x28: dfff800000000000 x27: 0000000000000000
x26: 0000000000000005 x25: ffff0000cd582bf8 x24: ffff00011c76e364
x23: ffff00011c76e358 x22: 1fffe000238edc62 x21: ffff00011c76e314
x20: ffff0000cd582c24 x19: ffff00011c76e280 x18: 0000000000000002
x17: 0000000000000002 x16: ffff8000119811d4 x15: 00000000ffffffff
x14: ffff0000cc1ed1c0 x13: 0000000000000001 x12: 0000000000040000
x11: 0000000000002dba x10: ffff800021cbd000 x9 : 568654ff41e5ff00
x8 : 568654ff41e5ff00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800021497198 x4 : ffff8000149ff8e0 x3 : ffff80000854d024
x2 : 0000000000000001 x1 : 0000000000000001 x0 : ffff800014c0faa0
Call trace:
proc_register+0x2e8/0x464 fs/proc/generic.c:378
proc_create_net_single+0x140/0x198 fs/proc/proc_net.c:209
bcm_connect+0x21c/0x448 net/can/bcm.c:1626
__sys_connect_file net/socket.c:1916 [inline]
__sys_connect+0x268/0x290 net/socket.c:1933
__do_sys_connect net/socket.c:1943 [inline]
__se_sys_connect net/socket.c:1940 [inline]
__arm64_sys_connect+0x7c/0x94 net/socket.c:1940
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 218
hardirqs last enabled at (217): [<ffff800008329e94>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (218): [<ffff80001197c860>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (206): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (206): [<ffff800008020ccc>] __do_softirq+0xb5c/0xdb0 kernel/softirq.c:587
softirqs last disabled at (77): [<ffff8000081b5568>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (77): [<ffff8000081b5568>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (77): [<ffff8000081b5568>] __irq_exit_rcu+0x264/0x4d4 kernel/softirq.c:637
---[ end trace 86ad1b84a5c48e9e ]---
---
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 syzk...@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
syzbot found the following issue on:
HEAD commit: 26c690eff0a5 Linux 5.15.146
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15df1683e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab948f7b303e76f8
dashboard link: https://syzkaller.appspot.com/bug?extid=e810231fb4eca8a972fd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/33e6f3a42ce6/disk-26c690ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0224f0ff4ede/vmlinux-26c690ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/822737ca97e0/Image-26c690ef.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e81023...@syzkaller.appspotmail.com
------------[ cut here ]------------
proc_dir_entry 'can-bcm/91548' already registered
WARNING: CPU: 1 PID: 23441 at fs/proc/generic.c:377 proc_register+0x2e8/0x464 fs/proc/generic.c:378
Modules linked in:
CPU: 1 PID: 23441 Comm: syz-executor.4 Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : proc_register+0x2e8/0x464 fs/proc/generic.c:378
lr : proc_register+0x2e0/0x464 fs/proc/generic.c:376
sp : ffff800021497a20
x29: ffff800021497a40 x28: dfff800000000000 x27: 0000000000000000
x26: 0000000000000005 x25: ffff0000cd582bf8 x24: ffff00011c76e364
x23: ffff00011c76e358 x22: 1fffe000238edc62 x21: ffff00011c76e314
x20: ffff0000cd582c24 x19: ffff00011c76e280 x18: 0000000000000002
x17: 0000000000000002 x16: ffff8000119811d4 x15: 00000000ffffffff
x14: ffff0000cc1ed1c0 x13: 0000000000000001 x12: 0000000000040000
x11: 0000000000002dba x10: ffff800021cbd000 x9 : 568654ff41e5ff00
x8 : 568654ff41e5ff00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800021497198 x4 : ffff8000149ff8e0 x3 : ffff80000854d024
x2 : 0000000000000001 x1 : 0000000000000001 x0 : ffff800014c0faa0
Call trace:
proc_register+0x2e8/0x464 fs/proc/generic.c:378
proc_create_net_single+0x140/0x198 fs/proc/proc_net.c:209
bcm_connect+0x21c/0x448 net/can/bcm.c:1626
__sys_connect_file net/socket.c:1916 [inline]
__sys_connect+0x268/0x290 net/socket.c:1933
__do_sys_connect net/socket.c:1943 [inline]
__se_sys_connect net/socket.c:1940 [inline]
__arm64_sys_connect+0x7c/0x94 net/socket.c:1940
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 218
hardirqs last enabled at (217): [<ffff800008329e94>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (218): [<ffff80001197c860>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (206): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (206): [<ffff800008020ccc>] __do_softirq+0xb5c/0xdb0 kernel/softirq.c:587
softirqs last disabled at (77): [<ffff8000081b5568>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (77): [<ffff8000081b5568>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (77): [<ffff8000081b5568>] __irq_exit_rcu+0x264/0x4d4 kernel/softirq.c:637
---[ end trace 86ad1b84a5c48e9e ]---
---
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 syzk...@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
syzbot
Jan 14, 2024, 6:26:20 AMJan 14
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 7c58bfa711cb Linux 6.1.72
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147aca0be80000
kernel config: https://syzkaller.appspot.com/x/.config?x=36d06871d6eebdd3
dashboard link: https://syzkaller.appspot.com/bug?extid=57466e050f2464381920
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b20a634d81c4/disk-7c58bfa7.raw.xz
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/d6a58728d5fa/vmlinux-7c58bfa7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c418bf23bed2/bzImage-7c58bfa7.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
------------[ cut here ]------------
proc_dir_entry 'can-bcm/178663' already registered
WARNING: CPU: 0 PID: 8789 at fs/proc/generic.c:377 proc_register+0x347/0x4e0 fs/proc/generic.c:376
Modules linked in:
CPU: 0 PID: 8789 Comm: syz-executor.0 Not tainted 6.1.72-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:proc_register+0x347/0x4e0 fs/proc/generic.c:376
Code: 7c 24 08 4c 8b 64 24 28 48 8b 6c 24 20 74 08 48 89 ef e8 ac e5 cb ff 48 8b 55 00 48 c7 c7 c0 af fb 8a 48 89 de e8 69 97 3c ff <0f> 0b 48 c7 c7 40 83 27 8d e8 3b ec 7e 08 48 8b 44 24 30 42 0f b6
RSP: 0018:ffffc9000f9afc48 EFLAGS: 00010246
RAX: f9649546e257ec00 RBX: ffff888097148364 RCX: 0000000000040000
RDX: ffffc90021229000 RSI: 0000000000006010 RDI: 0000000000006011
RBP: ffff88801f59d5d8 R08: ffffffff8152774e R09: fffff52001f35f29
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88801f59d594
R13: 0000000000000006 R14: dffffc0000000000 R15: ffff88801f59d500
FS: 00007ffa7183d6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f86d4300f63 CR3: 0000000086b79000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
proc_create_net_single+0x150/0x1a0 fs/proc/proc_net.c:219
bcm_connect+0x29e/0x490 net/can/bcm.c:1631
__sys_connect_file net/socket.c:2006 [inline]
__sys_connect+0x2c9/0x300 net/socket.c:2023
__do_sys_connect net/socket.c:2033 [inline]
__se_sys_connect net/socket.c:2030 [inline]
__x64_sys_connect+0x76/0x80 net/socket.c:2030
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ffa70a7cda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffa7183d0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: ffffffffffffffda RBX: 00007ffa70bac050 RCX: 00007ffa70a7cda9
RDX: 0000000000000010 RSI: 00000000200001c0 RDI: 0000000000000006
RBP: 00007ffa70ac947a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007ffa70bac050 R15: 00007ffe169f40f8
</TASK>
syzbot
Jan 14, 2024, 10:53:21 AMJan 14
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 26c690eff0a5 Linux 5.15.146
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=150531a3e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1622162be80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/33e6f3a42ce6/disk-26c690ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0224f0ff4ede/vmlinux-26c690ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/822737ca97e0/Image-26c690ef.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e81023...@syzkaller.appspotmail.com
__nla_validate_parse: 1 callbacks suppressed
netlink: 4 bytes leftover after parsing attributes in process `syz-executor312'.
------------[ cut here ]------------
proc_dir_entry 'can-bcm/24107' already registered
WARNING: CPU: 1 PID: 3993 at fs/proc/generic.c:377 proc_register+0x2e8/0x464 fs/proc/generic.c:378
Modules linked in:
CPU: 1 PID: 3993 Comm: syz-executor312 Not tainted 5.15.146-syzkaller #0
x29: ffff80001c6b7a40 x28: dfff800000000000 x27: 0000000000000000
x26: 0000000000000005 x25: ffff0000dc32ebf8 x24: ffff0000d05b5c24
x23: ffff0000d05b5c18 x22: 1fffe0001a0b6b7a x21: ffff0000d05b5bd4
x20: ffff0000dc32ec24 x19: ffff0000d05b5b40 x18: 0000000000000002
x17: 0000000000000000 x16: ffff8000119811d4 x15: 00000000ffffffff
x14: ffff0000cafb1b40 x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000000001 x10: 0000000000000000 x9 : 0a72980ad133ba00
x8 : 0a72980ad133ba00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001c6b7198 x4 : ffff8000149ff8e0 x3 : ffff80000854d024
x2 : 0000000000000001 x1 : 0000000100000001 x0 : ffff800014c0faa0
hardirqs last enabled at (1893): [<ffff800008329e94>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (1894): [<ffff80001197c860>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (1874): [<ffff80000fd41ca8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (1872): [<ffff80000fd41c74>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace be941dfbbac08da2 ]---
---
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.
HEAD commit: 26c690eff0a5 Linux 5.15.146
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=ab948f7b303e76f8
dashboard link: https://syzkaller.appspot.com/bug?extid=e810231fb4eca8a972fd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17503dcde80000
dashboard link: https://syzkaller.appspot.com/bug?extid=e810231fb4eca8a972fd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1622162be80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/33e6f3a42ce6/disk-26c690ef.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0224f0ff4ede/vmlinux-26c690ef.xz
kernel image: https://storage.googleapis.com/syzbot-assets/822737ca97e0/Image-26c690ef.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e81023...@syzkaller.appspotmail.com
netlink: 4 bytes leftover after parsing attributes in process `syz-executor312'.
------------[ cut here ]------------
proc_dir_entry 'can-bcm/24107' already registered
WARNING: CPU: 1 PID: 3993 at fs/proc/generic.c:377 proc_register+0x2e8/0x464 fs/proc/generic.c:378
Modules linked in:
CPU: 1 PID: 3993 Comm: syz-executor312 Not tainted 5.15.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : proc_register+0x2e8/0x464 fs/proc/generic.c:378
lr : proc_register+0x2e0/0x464 fs/proc/generic.c:376
sp : ffff80001c6b7a20
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : proc_register+0x2e8/0x464 fs/proc/generic.c:378
lr : proc_register+0x2e0/0x464 fs/proc/generic.c:376
x29: ffff80001c6b7a40 x28: dfff800000000000 x27: 0000000000000000
x26: 0000000000000005 x25: ffff0000dc32ebf8 x24: ffff0000d05b5c24
x23: ffff0000d05b5c18 x22: 1fffe0001a0b6b7a x21: ffff0000d05b5bd4
x20: ffff0000dc32ec24 x19: ffff0000d05b5b40 x18: 0000000000000002
x17: 0000000000000000 x16: ffff8000119811d4 x15: 00000000ffffffff
x14: ffff0000cafb1b40 x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000000001 x10: 0000000000000000 x9 : 0a72980ad133ba00
x8 : 0a72980ad133ba00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001c6b7198 x4 : ffff8000149ff8e0 x3 : ffff80000854d024
x2 : 0000000000000001 x1 : 0000000100000001 x0 : ffff800014c0faa0
Call trace:
proc_register+0x2e8/0x464 fs/proc/generic.c:378
proc_create_net_single+0x140/0x198 fs/proc/proc_net.c:209
bcm_connect+0x21c/0x448 net/can/bcm.c:1626
__sys_connect_file net/socket.c:1916 [inline]
__sys_connect+0x268/0x290 net/socket.c:1933
__do_sys_connect net/socket.c:1943 [inline]
__se_sys_connect net/socket.c:1940 [inline]
__arm64_sys_connect+0x7c/0x94 net/socket.c:1940
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 1894
proc_register+0x2e8/0x464 fs/proc/generic.c:378
proc_create_net_single+0x140/0x198 fs/proc/proc_net.c:209
bcm_connect+0x21c/0x448 net/can/bcm.c:1626
__sys_connect_file net/socket.c:1916 [inline]
__sys_connect+0x268/0x290 net/socket.c:1933
__do_sys_connect net/socket.c:1943 [inline]
__se_sys_connect net/socket.c:1940 [inline]
__arm64_sys_connect+0x7c/0x94 net/socket.c:1940
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
hardirqs last enabled at (1893): [<ffff800008329e94>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (1894): [<ffff80001197c860>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (1874): [<ffff80000fd41ca8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (1872): [<ffff80000fd41c74>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace be941dfbbac08da2 ]---
---
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.
syzbot
Jan 14, 2024, 5:17:23 PMJan 14
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 7c58bfa711cb Linux 6.1.72
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12efd925e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=faf1a88963777524
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e21a0be80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e09683e80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8706c723e078/disk-7c58bfa7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/09bb32ac1bde/vmlinux-7c58bfa7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/794945902a5c/Image-7c58bfa7.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+57466e...@syzkaller.appspotmail.com
__nla_validate_parse: 1 callbacks suppressed
netlink: 4 bytes leftover after parsing attributes in process `syz-executor351'.
------------[ cut here ]------------
proc_dir_entry 'can-bcm/25518' already registered
WARNING: CPU: 0 PID: 4244 at fs/proc/generic.c:377 proc_register+0x2e8/0x464 fs/proc/generic.c:378
Modules linked in:
CPU: 0 PID: 4244 Comm: syz-executor351 Not tainted 6.1.72-syzkaller #0
x29: ffff80001dd87a60 x28: dfff800000000000 x27: 0000000000000000
x26: 0000000000000005 x25: ffff0000dcde6ab8 x24: ffff0000dc1985e4
x23: ffff0000dc1985d8 x22: 1fffe0001b8330b2 x21: ffff0000dc198594
x20: ffff0000dcde6ae4 x19: ffff0000dc198500 x18: ffff80001dd86e40
x17: 0000000000000000 x16: ffff80001214c60c x15: 0000000000000000
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : eb97939b5a1f1c00
x8 : eb97939b5a1f1c00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001dd87338 x4 : ffff800015912b20 x3 : ffff8000085861e8
x2 : 0000000000000001 x1 : 0000000100000001 x0 : ffff800015b3e020
bcm_connect+0x220/0x438 net/can/bcm.c:1631
__sys_connect_file net/socket.c:2006 [inline]
__sys_connect+0x268/0x290 net/socket.c:2023
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 2232
hardirqs last enabled at (2231): [<ffff800008342ff8>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (2232): [<ffff8000121482c4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (2206): [<ffff8000103bae04>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (2204): [<ffff8000103badd0>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
HEAD commit: 7c58bfa711cb Linux 6.1.72
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=faf1a88963777524
dashboard link: https://syzkaller.appspot.com/bug?extid=57466e050f2464381920
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e21a0be80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e09683e80000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8706c723e078/disk-7c58bfa7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/09bb32ac1bde/vmlinux-7c58bfa7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/794945902a5c/Image-7c58bfa7.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+57466e...@syzkaller.appspotmail.com
netlink: 4 bytes leftover after parsing attributes in process `syz-executor351'.
------------[ cut here ]------------
proc_dir_entry 'can-bcm/25518' already registered
WARNING: CPU: 0 PID: 4244 at fs/proc/generic.c:377 proc_register+0x2e8/0x464 fs/proc/generic.c:378
Modules linked in:
CPU: 0 PID: 4244 Comm: syz-executor351 Not tainted 6.1.72-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : proc_register+0x2e8/0x464 fs/proc/generic.c:378
lr : proc_register+0x2e0/0x464 fs/proc/generic.c:376
sp : ffff80001dd87a40
pc : proc_register+0x2e8/0x464 fs/proc/generic.c:378
lr : proc_register+0x2e0/0x464 fs/proc/generic.c:376
x29: ffff80001dd87a60 x28: dfff800000000000 x27: 0000000000000000
x26: 0000000000000005 x25: ffff0000dcde6ab8 x24: ffff0000dc1985e4
x23: ffff0000dc1985d8 x22: 1fffe0001b8330b2 x21: ffff0000dc198594
x20: ffff0000dcde6ae4 x19: ffff0000dc198500 x18: ffff80001dd86e40
x17: 0000000000000000 x16: ffff80001214c60c x15: 0000000000000000
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : eb97939b5a1f1c00
x8 : eb97939b5a1f1c00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001dd87338 x4 : ffff800015912b20 x3 : ffff8000085861e8
x2 : 0000000000000001 x1 : 0000000100000001 x0 : ffff800015b3e020
Call trace:
proc_register+0x2e8/0x464 fs/proc/generic.c:378
proc_create_net_single+0x140/0x198 fs/proc/proc_net.c:219
proc_register+0x2e8/0x464 fs/proc/generic.c:378
bcm_connect+0x220/0x438 net/can/bcm.c:1631
__sys_connect_file net/socket.c:2006 [inline]
__sys_connect+0x268/0x290 net/socket.c:2023
__do_sys_connect net/socket.c:2033 [inline]
__se_sys_connect net/socket.c:2030 [inline]
__arm64_sys_connect+0x7c/0x94 net/socket.c:2030
__se_sys_connect net/socket.c:2030 [inline]
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 2232
hardirqs last enabled at (2231): [<ffff800008342ff8>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (2232): [<ffff8000121482c4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (2206): [<ffff8000103bae04>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (2204): [<ffff8000103badd0>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---
Reply all
Reply to author
Forward
0 new messages