linux-kernel - WARNING in kernfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Tue, 08 Sep 2020 11:19:17 -0700
From:   syzbot <syzbot+d41ab07507be715b63f5@...kaller.appspotmail.com>
To:     gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com, tj@...nel.org
Subject: WARNING in kernfs_get (2)

Hello,

syzbot found the following issue on:

HEAD commit:    7a695657 Add linux-next specific files for 20200903
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14089ff5900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=39134fcec6c78e33
dashboard link: https://syzkaller.appspot.com/bug?extid=d41ab07507be715b63f5
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+d41ab07507be715b63f5@...kaller.appspotmail.com

tipc: TX() has been purged, node left!
------------[ cut here ]------------
WARNING: CPU: 1 PID: 12334 at fs/kernfs/dir.c:494 kernfs_get.part.0+0x69/0x80 fs/kernfs/dir.c:494
Modules linked in:
CPU: 1 PID: 12334 Comm: kworker/u4:0 Not tainted 5.9.0-rc3-next-20200903-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: netns cleanup_net
RIP: 0010:kernfs_get.part.0+0x69/0x80 fs/kernfs/dir.c:494
Code: 31 ff 89 ee e8 38 14 8b ff 85 ed 74 18 e8 af 17 8b ff be 04 00 00 00 48 89 df e8 22 5e cb ff f0 ff 03 5b 5d c3 e8 97 17 8b ff <0f> 0b eb df 48 89 df e8 eb 8b cb ff eb c6 66 0f 1f 84 00 00 00 00
RSP: 0018:ffffc9001579f730 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88800018bb20 RCX: ffffffff81e9cb48
RDX: ffff888054612200 RSI: ffffffff81e9cb69 RDI: 0000000000000005
RBP: 0000000000000000 R08: 0000000000000000 R09: ffff88800018bb23
R10: 0000000000000000 R11: 000000000000016e R12: 0000000000000000
R13: 0000000000000000 R14: dffffc0000000000 R15: ffff88800018bb20
FS:  0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055594cc40180 CR3: 000000005d64c000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 kernfs_get fs/kernfs/dir.c:493 [inline]
 __kernfs_remove+0x299/0xa30 fs/kernfs/dir.c:1314
 kernfs_remove_by_name_ns+0x51/0xb0 fs/kernfs/dir.c:1516
 kernfs_remove_by_name include/linux/kernfs.h:593 [inline]
 remove_files+0x96/0x1c0 fs/sysfs/group.c:28
 sysfs_remove_group+0x87/0x170 fs/sysfs/group.c:289
 sysfs_remove_groups fs/sysfs/group.c:313 [inline]
 sysfs_remove_groups+0x5c/0xa0 fs/sysfs/group.c:305
 device_remove_groups drivers/base/core.c:2033 [inline]
 device_remove_attrs+0xba/0x160 drivers/base/core.c:2224
 device_del+0x479/0xd90 drivers/base/core.c:3108
 rollback_registered_many+0xb16/0x1210 net/core/dev.c:9311
 unregister_netdevice_many.part.0+0x1a/0x2f0 net/core/dev.c:10429
 unregister_netdevice_many+0x36/0x50 net/core/dev.c:10428
 ip_tunnel_delete_nets+0x3da/0x580 net/ipv4/ip_tunnel.c:1125
 ops_exit_list+0x10d/0x160 net/core/net_namespace.c:189
 cleanup_net+0x4ea/0xb10 net/core/net_namespace.c:603
 process_one_work+0x94c/0x1670 kernel/workqueue.c:2269
 worker_thread+0x64c/0x1120 kernel/workqueue.c:2415
 kthread+0x3b5/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294


---
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@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.