WARNING in sysfs_warn_dup

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 015e94d0 Linux 4.19.146
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14bf3cc3900000
kernel config: https://syzkaller.appspot.com/x/.config?x=243dd74ad58a8a57
dashboard link: https://syzkaller.appspot.com/bug?extid=9764ee1ef5efbba9d13d
compiler: gcc (GCC) 10.1.0-syz 20200507

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+9764ee...@syzkaller.appspotmail.com

sysfs: cannot create duplicate filename '/class/ieee80211/ M! �)v�S�'
------------[ cut here ]------------
CPU: 0 PID: 20688 Comm: syz-executor.0 Not tainted 4.19.146-syzkaller #0
WARNING: CPU: 1 PID: 20654 at fs/f2fs/checkpoint.c:166 f2fs_is_valid_blkaddr+0x5bd/0xa90 fs/f2fs/checkpoint.c:166
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Kernel panic - not syncing: panic_on_warn set ...

Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
sysfs_warn_dup.cold+0x1c/0x2d fs/sysfs/dir.c:30
sysfs_do_create_link_sd+0x122/0x140 fs/sysfs/symlink.c:50
sysfs_do_create_link fs/sysfs/symlink.c:79 [inline]
sysfs_create_link+0x5f/0xc0 fs/sysfs/symlink.c:91
device_add_class_symlinks drivers/base/core.c:1918 [inline]
device_add+0x6c9/0x1550 drivers/base/core.c:2120
wiphy_register+0x16f4/0x22b0 net/wireless/core.c:832
ieee80211_register_hw+0x1645/0x3580 net/mac80211/main.c:1092
mac80211_hwsim_new_radio+0x1f5c/0x4070 drivers/net/wireless/mac80211_hwsim.c:2896
hwsim_new_radio_nl+0x5ef/0x8b0 drivers/net/wireless/mac80211_hwsim.c:3374
genl_family_rcv_msg+0x6bf/0xd50 net/netlink/genetlink.c:602
genl_rcv_msg+0xdf/0x1b0 net/netlink/genetlink.c:627
netlink_rcv_skb+0x160/0x440 net/netlink/af_netlink.c:2455
genl_rcv+0x24/0x40 net/netlink/genetlink.c:638
netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]
netlink_unicast+0x4d5/0x690 net/netlink/af_netlink.c:1344
netlink_sendmsg+0x717/0xcc0 net/netlink/af_netlink.c:1909
sock_sendmsg_nosec net/socket.c:622 [inline]
sock_sendmsg+0xc7/0x130 net/socket.c:632
___sys_sendmsg+0x7bb/0x8f0 net/socket.c:2115
__sys_sendmsg net/socket.c:2153 [inline]
__do_sys_sendmsg net/socket.c:2162 [inline]
__se_sys_sendmsg net/socket.c:2160 [inline]
__x64_sys_sendmsg+0x132/0x220 net/socket.c:2160
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45e179
Code: 3d b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 0b b2 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f213e742c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002cd80 RCX: 000000000045e179
RDX: 0000000000000000 RSI: 0000000020000080 RDI: 0000000000000005
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffd3ce643ef R14: 00007f213e7439c0 R15: 000000000118cf4c
CPU: 1 PID: 20654 Comm: syz-executor.1 Not tainted 4.19.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x22c/0x33e lib/dump_stack.c:118
panic+0x2ac/0x565 kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:186
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1e1/0x330 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:f2fs_is_valid_blkaddr+0x5bd/0xa90 fs/f2fs/checkpoint.c:166
Code: 90 04 00 00 48 8b 7d 00 44 89 e1 48 c7 c2 80 ce 47 88 48 c7 c6 a0 cb 47 88 e8 0f d8 fd ff 48 c7 c7 c0 ce 47 88 e8 82 f0 23 fe <0f> 0b 45 31 e4 e9 e3 fb ff ff e8 44 75 3a fe 48 8d bd 5c 0d 00 00
RSP: 0018:ffff8880463af720 EFLAGS: 00010286
RAX: 0000000000000024 RBX: 0000000000000005 RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff815b523f RDI: ffffed1008c75ed6
RBP: ffff88804b5d8900 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000001400 R14: 0000000000004000 R15: ffff88804b5d8a40
f2fs_submit_page_bio+0x19a/0x15e0 fs/f2fs/data.c:450
read_node_page+0x496/0x660 fs/f2fs/node.c:1303
__get_node_page.part.0+0x9b/0x1540 fs/f2fs/node.c:1348
__get_node_page fs/f2fs/node.c:38 [inline]
f2fs_get_node_page+0x109/0x1a0 fs/f2fs/node.c:1394
do_read_inode fs/f2fs/inode.c:306 [inline]
f2fs_iget+0x22a/0x4e90 fs/f2fs/inode.c:439
f2fs_fill_super+0x243d/0x7920 fs/f2fs/super.c:3056
mount_bdev+0x2fc/0x3b0 fs/super.c:1158
mount_fs+0xa3/0x318 fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2469 [inline]
do_mount+0x51c/0x2f10 fs/namespace.c:2799
ksys_mount+0xcf/0x130 fs/namespace.c:3015
__do_sys_mount fs/namespace.c:3029 [inline]
__se_sys_mount fs/namespace.c:3026 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3026
do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x460bca
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 dd 87 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 ba 87 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007fe3a42daa88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fe3a42dab20 RCX: 0000000000460bca
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fe3a42daae0
RBP: 00007fe3a42daae0 R08: 00007fe3a42dab20 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 0000000020000200 R15: 0000000020014b00
Kernel Offset: disabled
Rebooting in 86400 seconds..


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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.