netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [syzbot] WARNING in print_bfs_bug (2)
@ 2022-12-29 15:51 syzbot
  2023-04-29 13:38 ` [syzbot] [net?] " syzbot
  2023-04-29 22:54 ` syzbot
  0 siblings, 2 replies; 5+ messages in thread
From: syzbot @ 2022-12-29 15:51 UTC (permalink / raw)
  To: davem, edumazet, jiri, kuba, linux-kernel, netdev, pabeni,
	syzkaller-bugs

Hello,

syzbot found the following issue on:

HEAD commit:    72a85e2b0a1e Merge tag 'spi-fix-v6.2-rc1' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10127b44480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b0e81c4eb13a67cd
dashboard link: https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bf5b7ea54f05/disk-72a85e2b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cd3c30b473ee/vmlinux-72a85e2b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/df9aad922f68/bzImage-72a85e2b.xz

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

device team1929 entered promiscuous mode
8021q: adding VLAN 0 to HW filter on device team1929
------------[ cut here ]------------
lockdep bfs error:-1
WARNING: CPU: 0 PID: 17604 at kernel/locking/lockdep.c:2066 print_bfs_bug+0x22/0x30 kernel/locking/lockdep.c:2066
Modules linked in:
CPU: 0 PID: 17604 Comm: syz-executor.2 Not tainted 6.1.0-syzkaller-14594-g72a85e2b0a1e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:print_bfs_bug+0x22/0x30 kernel/locking/lockdep.c:2066
Code: 84 00 00 00 00 00 66 90 55 89 fd 53 e8 17 67 a5 02 89 c3 e8 60 fd ff ff 85 db 74 10 89 ee 48 c7 c7 20 42 4c 8a e8 c3 48 5c 08 <0f> 0b 5b 5d c3 66 0f 1f 84 00 00 00 00 00 41 57 be fd ff 0f 00 41
RSP: 0018:ffffc90016386800 EFLAGS: 00010082
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff8165927c RDI: fffff52002c70cf2
RBP: 00000000ffffffff R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000002 R11: 207065646b636f6c R12: ffff8881bee94d08
R13: ffff8881bee94d30 R14: ffff8881bee94280 R15: ffffc90016386910
FS:  00007f3023c34700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f589d7a6cc4 CR3: 00000001b2879000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 check_irq_usage+0x69a/0xab0 kernel/locking/lockdep.c:2791
 check_prev_add kernel/locking/lockdep.c:3101 [inline]
 check_prevs_add kernel/locking/lockdep.c:3216 [inline]
 validate_chain kernel/locking/lockdep.c:3831 [inline]
 __lock_acquire+0x2a5b/0x56d0 kernel/locking/lockdep.c:5055
 lock_acquire kernel/locking/lockdep.c:5668 [inline]
 lock_acquire+0x1e3/0x630 kernel/locking/lockdep.c:5633
 do_write_seqcount_begin_nested include/linux/seqlock.h:516 [inline]
 do_write_seqcount_begin include/linux/seqlock.h:541 [inline]
 psi_group_change+0x138/0xc10 kernel/sched/psi.c:775
 psi_task_switch+0x582/0x930 kernel/sched/psi.c:926
 psi_sched_switch kernel/sched/stats.h:185 [inline]
 __schedule+0x379b/0x5450 kernel/sched/core.c:6550
 preempt_schedule_common+0x45/0xc0 kernel/sched/core.c:6724
 preempt_schedule_thunk+0x1a/0x20 arch/x86/entry/thunk_64.S:34
 __mutex_lock_common kernel/locking/mutex.c:728 [inline]
 __mutex_lock+0xfff/0x1360 kernel/locking/mutex.c:747
 team_vlan_rx_add_vid+0x3c/0x1e0 drivers/net/team/team.c:1906
 vlan_add_rx_filter_info+0x149/0x1d0 net/8021q/vlan_core.c:211
 __vlan_vid_add net/8021q/vlan_core.c:306 [inline]
 vlan_vid_add+0x3f6/0x7f0 net/8021q/vlan_core.c:336
 vlan_device_event.cold+0x28/0x2d net/8021q/vlan.c:385
 notifier_call_chain+0xb5/0x200 kernel/notifier.c:87
 call_netdevice_notifiers_info+0xb5/0x130 net/core/dev.c:1944
 call_netdevice_notifiers_extack net/core/dev.c:1982 [inline]
 call_netdevice_notifiers net/core/dev.c:1996 [inline]
 __dev_notify_flags+0x120/0x2d0 net/core/dev.c:8569
 rtnl_configure_link+0x181/0x260 net/core/rtnetlink.c:3241
 rtnl_newlink_create net/core/rtnetlink.c:3415 [inline]
 __rtnl_newlink+0x10f6/0x1840 net/core/rtnetlink.c:3624
 rtnl_newlink+0x68/0xa0 net/core/rtnetlink.c:3637
 rtnetlink_rcv_msg+0x43e/0xca0 net/core/rtnetlink.c:6141
 netlink_rcv_skb+0x165/0x440 net/netlink/af_netlink.c:2564
 netlink_unicast_kernel net/netlink/af_netlink.c:1330 [inline]
 netlink_unicast+0x547/0x7f0 net/netlink/af_netlink.c:1356
 netlink_sendmsg+0x91b/0xe10 net/netlink/af_netlink.c:1932
 sock_sendmsg_nosec net/socket.c:714 [inline]
 sock_sendmsg+0xd3/0x120 net/socket.c:734
 ____sys_sendmsg+0x712/0x8c0 net/socket.c:2476
 ___sys_sendmsg+0x110/0x1b0 net/socket.c:2530
 __sys_sendmsg+0xf7/0x1c0 net/socket.c:2559
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f3022e8c0a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3023c34168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007f3022fabf80 RCX: 00007f3022e8c0a9
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000007
RBP: 00007f3022ee7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffeb966cb2f R14: 00007f3023c34300 R15: 0000000000022000
 </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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] [net?] WARNING in print_bfs_bug (2)
  2022-12-29 15:51 [syzbot] WARNING in print_bfs_bug (2) syzbot
@ 2023-04-29 13:38 ` syzbot
  2023-04-29 22:54 ` syzbot
  1 sibling, 0 replies; 5+ messages in thread
From: syzbot @ 2023-04-29 13:38 UTC (permalink / raw)
  To: davem, edumazet, jiri, kuba, linux-kernel, netdev, pabeni,
	syzkaller-bugs

syzbot has found a reproducer for the following issue on:

HEAD commit:    042334a8d424 atlantic:hw_atl2:hw_atl2_utils_fw: Remove unn..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11869168280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7205cdba522fe4bc
dashboard link: https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=147328f8280000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1665151c280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e9818e554a99/disk-042334a8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/de8daea0ee8b/vmlinux-042334a8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/71f9842dcf98/bzImage-042334a8.xz

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

netlink: 4 bytes leftover after parsing attributes in process `syz-executor204'.
------------[ cut here ]------------
lockdep bfs error:-1
WARNING: CPU: 0 PID: 10222 at kernel/locking/lockdep.c:2077 print_bfs_bug+0x22/0x30 kernel/locking/lockdep.c:2077
Modules linked in:
CPU: 0 PID: 10222 Comm: syz-executor204 Not tainted 6.3.0-syzkaller-07921-g042334a8d424 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:print_bfs_bug+0x22/0x30 kernel/locking/lockdep.c:2077
Code: 84 00 00 00 00 00 66 90 55 89 fd 53 e8 c7 34 a9 02 89 c3 e8 60 fd ff ff 85 db 74 10 89 ee 48 c7 c7 20 68 4c 8a e8 3e bb e7 ff <0f> 0b 5b 5d c3 66 0f 1f 84 00 00 00 00 00 53 31 c9 31 d2 31 f6 48
RSP: 0018:ffffc9000e906ba0 EFLAGS: 00010082
RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff888021769dc0 RSI: ffffffff814bef47 RDI: 0000000000000001
RBP: 00000000ffffffff R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: ffff88802176a950
R13: 0000000000000037 R14: ffffc9000e906cc8 R15: 0000000000000000
FS:  0000555556212300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6c98af3140 CR3: 000000002236d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 check_irq_usage+0x56c/0x1a40 kernel/locking/lockdep.c:2845
 check_prev_add kernel/locking/lockdep.c:3112 [inline]
 check_prevs_add kernel/locking/lockdep.c:3227 [inline]
 validate_chain kernel/locking/lockdep.c:3842 [inline]
 __lock_acquire+0x2f39/0x5df0 kernel/locking/lockdep.c:5074
 lock_acquire kernel/locking/lockdep.c:5691 [inline]
 lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5656
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
 mm_cid_put kernel/sched/sched.h:3270 [inline]
 mm_cid_put kernel/sched/sched.h:3265 [inline]
 switch_mm_cid kernel/sched/sched.h:3298 [inline]
 prepare_task_switch kernel/sched/core.c:5117 [inline]
 context_switch kernel/sched/core.c:5258 [inline]
 __schedule+0x26a3/0x5770 kernel/sched/core.c:6625
 preempt_schedule_common+0x45/0xb0 kernel/sched/core.c:6794
 preempt_schedule_thunk+0x1a/0x20 arch/x86/entry/thunk_64.S:34
 __mutex_lock_common kernel/locking/mutex.c:728 [inline]
 __mutex_lock+0xfe5/0x1350 kernel/locking/mutex.c:747
 team_nl_team_get+0x10f/0x1c0 drivers/net/team/team.c:2320
 team_nl_cmd_options_set+0xa0/0xc80 drivers/net/team/team.c:2543
 genl_family_rcv_msg_doit.isra.0+0x1e6/0x2d0 net/netlink/genetlink.c:968
 genl_family_rcv_msg net/netlink/genetlink.c:1048 [inline]
 genl_rcv_msg+0x4ff/0x7e0 net/netlink/genetlink.c:1065
 netlink_rcv_skb+0x165/0x440 net/netlink/af_netlink.c:2546
 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1076
 netlink_unicast_kernel net/netlink/af_netlink.c:1339 [inline]
 netlink_unicast+0x547/0x7f0 net/netlink/af_netlink.c:1365
 netlink_sendmsg+0x925/0xe30 net/netlink/af_netlink.c:1913
 sock_sendmsg_nosec net/socket.c:724 [inline]
 sock_sendmsg+0xde/0x190 net/socket.c:747
 ____sys_sendmsg+0x71c/0x900 net/socket.c:2503
 ___sys_sendmsg+0x110/0x1b0 net/socket.c:2557
 __sys_sendmsg+0xf7/0x1c0 net/socket.c:2586
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f6c98a82b29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 14 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd09390778 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00000000000eee12 RCX: 00007f6c98a82b29
RDX: 0000000000000000 RSI: 0000000020000000 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: 00007ffd09390918
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd0939078c
R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000
 </TASK>


---
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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] [net?] WARNING in print_bfs_bug (2)
  2022-12-29 15:51 [syzbot] WARNING in print_bfs_bug (2) syzbot
  2023-04-29 13:38 ` [syzbot] [net?] " syzbot
@ 2023-04-29 22:54 ` syzbot
  2023-05-03  2:49   ` Tzung-Bi Shih
  1 sibling, 1 reply; 5+ messages in thread
From: syzbot @ 2023-04-29 22:54 UTC (permalink / raw)
  To: broonie, davem, edumazet, groeck, jiri, kuba, linmq006,
	linux-fsdevel, linux-kernel, netdev, pabeni, syzkaller-bugs,
	tzungbi, viro

syzbot has bisected this issue to:

commit 0a034d93ee929a9ea89f3fa5f1d8492435b9ee6e
Author: Miaoqian Lin <linmq006@gmail.com>
Date:   Fri Jun 3 13:10:43 2022 +0000

    ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13d40608280000
start commit:   042334a8d424 atlantic:hw_atl2:hw_atl2_utils_fw: Remove unn..
git tree:       net-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=10340608280000
console output: https://syzkaller.appspot.com/x/log.txt?x=17d40608280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=7205cdba522fe4bc
dashboard link: https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=147328f8280000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1665151c280000

Reported-by: syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com
Fixes: 0a034d93ee92 ("ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] [net?] WARNING in print_bfs_bug (2)
  2023-04-29 22:54 ` syzbot
@ 2023-05-03  2:49   ` Tzung-Bi Shih
  2023-05-05 13:27     ` Mark Brown
  0 siblings, 1 reply; 5+ messages in thread
From: Tzung-Bi Shih @ 2023-05-03  2:49 UTC (permalink / raw)
  To: syzbot
  Cc: broonie, davem, edumazet, groeck, jiri, kuba, linmq006,
	linux-fsdevel, linux-kernel, netdev, pabeni, syzkaller-bugs,
	viro

On Sat, Apr 29, 2023 at 03:54:28PM -0700, syzbot wrote:
> syzbot has bisected this issue to:
> 
> commit 0a034d93ee929a9ea89f3fa5f1d8492435b9ee6e
> Author: Miaoqian Lin <linmq006@gmail.com>
> Date:   Fri Jun 3 13:10:43 2022 +0000
> 
>     ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13d40608280000
> start commit:   042334a8d424 atlantic:hw_atl2:hw_atl2_utils_fw: Remove unn..
> git tree:       net-next
> final oops:     https://syzkaller.appspot.com/x/report.txt?x=10340608280000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17d40608280000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=7205cdba522fe4bc
> dashboard link: https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=147328f8280000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1665151c280000
> 
> Reported-by: syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com
> Fixes: 0a034d93ee92 ("ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe")

I failed to see the connection between the oops and commit 0a034d93ee92.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [syzbot] [net?] WARNING in print_bfs_bug (2)
  2023-05-03  2:49   ` Tzung-Bi Shih
@ 2023-05-05 13:27     ` Mark Brown
  0 siblings, 0 replies; 5+ messages in thread
From: Mark Brown @ 2023-05-05 13:27 UTC (permalink / raw)
  To: Tzung-Bi Shih
  Cc: syzbot, davem, edumazet, groeck, jiri, kuba, linmq006,
	linux-fsdevel, linux-kernel, netdev, pabeni, syzkaller-bugs,
	viro

[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]

On Wed, May 03, 2023 at 10:49:31AM +0800, Tzung-Bi Shih wrote:
> On Sat, Apr 29, 2023 at 03:54:28PM -0700, syzbot wrote:
> > syzbot has bisected this issue to:
> > 
> > commit 0a034d93ee929a9ea89f3fa5f1d8492435b9ee6e
> > Author: Miaoqian Lin <linmq006@gmail.com>
> > Date:   Fri Jun 3 13:10:43 2022 +0000
> > 
> >     ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe
> > 
> > bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13d40608280000
> > start commit:   042334a8d424 atlantic:hw_atl2:hw_atl2_utils_fw: Remove unn..
> > git tree:       net-next
> > final oops:     https://syzkaller.appspot.com/x/report.txt?x=10340608280000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=17d40608280000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=7205cdba522fe4bc
> > dashboard link: https://syzkaller.appspot.com/bug?extid=630f83b42d801d922b8b
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=147328f8280000
> > C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1665151c280000
> > 
> > Reported-by: syzbot+630f83b42d801d922b8b@syzkaller.appspotmail.com
> > Fixes: 0a034d93ee92 ("ASoC: cros_ec_codec: Fix refcount leak in cros_ec_codec_platform_probe")

> I failed to see the connection between the oops and commit 0a034d93ee92.

syzbot seems to generate a *lot* of false positives, this looks like one
of them so it's probably safe to ignore the bisection.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-05-05 13:27 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-29 15:51 [syzbot] WARNING in print_bfs_bug (2) syzbot
2023-04-29 13:38 ` [syzbot] [net?] " syzbot
2023-04-29 22:54 ` syzbot
2023-05-03  2:49   ` Tzung-Bi Shih
2023-05-05 13:27     ` Mark Brown

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).