[moderation/CI] Re: namespace-aware configfs

[syzbot ci]

syzbot ci has tested the following series

[v2] namespace-aware configfs
https://lore.kernel.org/all/20260619-configfs-n...@kernel.org
* [PATCH RFC v2 01/12] fs/configfs: rework configfs_is_root()
* [PATCH RFC v2 02/12] fs/configfs: dynamically allocate super_info
* [PATCH RFC v2 03/12] fs/configfs: separate out configfs_{link,unlink}_root()
* [PATCH RFC v2 04/12] fs/configfs: add superblock as attribute to configfs_pin_fs()
* [PATCH RFC v2 05/12] fs/configfs: add 'fill_subsystem' and 'clear_subsystem' callbacks
* [PATCH RFC v2 06/12] fs/configfs: add superblock as attribute to configfs_pin_fs()
* [PATCH RFC v2 07/12] fs/namespace: implement mnt_clone_direct()
* [PATCH RFC v2 08/12] fs/configfs: switch to get_tree_keyed()
* [PATCH RFC v2 09/12] fs/configfs: open-code simple_pin_fs()
* [PATCH RFC v2 10/12] nvmet: make discovery subsystem dynamic
* [PATCH RFC v2 11/12] nvmet: per net-namespace port list
* [PATCH RFC v2 12/12] nvmet: make configfs setup namespace aware

and found the following issue:
general protection fault in put_net

Full report is available here:
https://ci.syzbot.org/series/dd681b97-ec65-4bbf-9440-cbbf1c103062

***

general protection fault in put_net

tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 66affa37cfac0aec061cc4bcf4a065b0c52f7e19
arch: amd64
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config: https://ci.syzbot.org/builds/a4aeaf5c-a583-4650-97af-058d35909234/config
syz repro: https://ci.syzbot.org/findings/773be3e5-366e-482f-8da3-9a5abb71b7a8/syz_repro

Oops: general protection fault, probably for non-canonical address 0xdffffc000000003b: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x00000000000001d8-0x00000000000001df]
CPU: 0 UID: 0 PID: 5865 Comm: syz.1.18 Tainted: G W syzkaller #0 PREEMPT(full)
Tainted: [W]=WARN
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:is_ns_init_id include/linux/ns_common.h:25 [inline]
RIP: 0010:__ns_ref_put include/linux/ns_common.h:72 [inline]
RIP: 0010:put_net+0x33/0x260 include/net/net_namespace.h:297
Code: 53 48 89 fb e8 4e ea 50 ff 48 85 db 0f 84 e8 00 00 00 49 bc 00 00 00 00 00 fc ff df 4c 8d b3 e0 01 00 00 4d 89 f5 49 c1 ed 03 <43> 80 7c 25 00 00 74 08 4c 89 f7 e8 6d 1d be ff 4d 8b 3e 31 ff 4c
RSP: 0018:ffffc9000349fcb8 EFLAGS: 00010203
RAX: ffffffff8275a0b2 RBX: fffffffffffffffd RCX: ffff88810d921dc0
RDX: 0000000000000000 RSI: 0000000000010000 RDI: fffffffffffffffd
RBP: 0000000000010000 R08: ffffffff903203f7 R09: 1ffffffff206407e
R10: dffffc0000000000 R11: ffffffff8275aa40 R12: dffffc0000000000
R13: 000000000000003b R14: 00000000000001dd R15: 0000000000000000
FS: 000055558a1a8500(0000) GS:ffff88818dc4e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33263fff CR3: 0000000116edc000 CR4: 00000000000006f0
Call Trace:
<TASK>
put_fs_context+0x123/0xb00 fs/fs_context.c:498
fscontext_release+0x62/0x80 fs/fsopen.c:79
__fput+0x44f/0xa60 fs/file_table.c:512
task_work_run+0x1d9/0x270 kernel/task_work.c:233
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
__exit_to_user_mode_loop kernel/entry/common.c:70 [inline]
exit_to_user_mode_loop+0x1fa/0x710 kernel/entry/common.c:101
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:230 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline]
do_syscall_64+0x353/0x580 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb902f9ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff92660ec8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007fff92660fb0 RCX: 00007fb902f9ce59
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 00000000000107a6 R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b32620000 R11: 0000000000000246 R12: 00007fff92660ff0
R13: 00007fb903215fac R14: 00000000000107da R15: 00007fb903215fa0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:is_ns_init_id include/linux/ns_common.h:25 [inline]
RIP: 0010:__ns_ref_put include/linux/ns_common.h:72 [inline]
RIP: 0010:put_net+0x33/0x260 include/net/net_namespace.h:297
Code: 53 48 89 fb e8 4e ea 50 ff 48 85 db 0f 84 e8 00 00 00 49 bc 00 00 00 00 00 fc ff df 4c 8d b3 e0 01 00 00 4d 89 f5 49 c1 ed 03 <43> 80 7c 25 00 00 74 08 4c 89 f7 e8 6d 1d be ff 4d 8b 3e 31 ff 4c
RSP: 0018:ffffc9000349fcb8 EFLAGS: 00010203
RAX: ffffffff8275a0b2 RBX: fffffffffffffffd RCX: ffff88810d921dc0
RDX: 0000000000000000 RSI: 0000000000010000 RDI: fffffffffffffffd
RBP: 0000000000010000 R08: ffffffff903203f7 R09: 1ffffffff206407e
R10: dffffc0000000000 R11: ffffffff8275aa40 R12: dffffc0000000000
R13: 000000000000003b R14: 00000000000001dd R15: 0000000000000000
FS: 000055558a1a8500(0000) GS:ffff88818dc4e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33263fff CR3: 0000000116edc000 CR4: 00000000000006f0
----------------
Code disassembly (best guess):
0: 53 push %rbx
1: 48 89 fb mov %rdi,%rbx
4: e8 4e ea 50 ff call 0xff50ea57
9: 48 85 db test %rbx,%rbx
c: 0f 84 e8 00 00 00 je 0xfa
12: 49 bc 00 00 00 00 00 movabs $0xdffffc0000000000,%r12
19: fc ff df
1c: 4c 8d b3 e0 01 00 00 lea 0x1e0(%rbx),%r14
23: 4d 89 f5 mov %r14,%r13
26: 49 c1 ed 03 shr $0x3,%r13
* 2a: 43 80 7c 25 00 00 cmpb $0x0,0x0(%r13,%r12,1) <-- trapping instruction
30: 74 08 je 0x3a
32: 4c 89 f7 mov %r14,%rdi
35: e8 6d 1d be ff call 0xffbe1da7
3a: 4d 8b 3e mov (%r14),%r15
3d: 31 ff xor %edi,%edi
3f: 4c rex.WR


***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@googlegroups.com.

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:
[a.hin...@kernel.org bra...@kernel.org ha...@kernel.org ha...@suse.de h...@lst.de ja...@suse.cz k...@nvidia.com lei...@debian.org linux-...@vger.kernel.org linux-...@vger.kernel.org linux...@lists.infradead.org sa...@grimberg.me vi...@zeniv.linux.org.uk]

If the report looks fine to you, reply with:
#syz upstream

If the report is a false positive, reply with
#syz invalid

[Pimyn Girgis]

#syz upstream

> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6a354228.6d5abbec.a50f.002f.GAE%40google.com.



--
Ⲡⲟⲓⲙⲏⲛ Ⲅⲉⲱⲣⲅⲓⲟⲥ - Pimyn Girgis
Software Engineer
Kernel Dynamic Analysis
pi...@google.com

[syzbot ci]

syzbot ci has tested the following series

[v3] namespace-aware configfs
https://lore.kernel.org/all/20260623-configfs-n...@kernel.org
* [PATCH RFC v3 01/12] fs/configfs: rework configfs_is_root()
* [PATCH RFC v3 02/12] fs/configfs: dynamically allocate super_info
* [PATCH RFC v3 03/12] fs/configfs: separate out configfs_{link,unlink}_root()
* [PATCH RFC v3 04/12] fs/configfs: add superblock as attribute to configfs_pin_fs()
* [PATCH RFC v3 05/12] fs/configfs: add 'fill_subsystem' and 'clear_subsystem' callbacks
* [PATCH RFC v3 06/12] fs/namespace: implement mnt_clone_direct()
* [PATCH RFC v3 07/12] fs/configfs: switch to get_tree_keyed()
* [PATCH RFC v3 08/12] fs/configfs: open-code simple_pin_fs()
* [PATCH RFC v3 09/12] nvmet: make discovery subsystem dynamic
* [PATCH RFC v3 10/12] nvmet: per net-namespace port list
* [PATCH RFC v3 11/12] nvmet: make configfs setup namespace aware
* [PATCH RFC v3 12/12] nvmet: enable transports for net namespaces

and found the following issue:

BUG: sleeping function called from invalid context in configfs_get_super_info

Full report is available here:

https://ci.syzbot.org/series/f460be5a-d520-4bc1-9cfb-6492f841629b

***

BUG: sleeping function called from invalid context in configfs_get_super_info

tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 66affa37cfac0aec061cc4bcf4a065b0c52f7e19
arch: amd64

compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/73803fa0-5ba4-4d03-976f-f9962ee982c8/config
syz repro: https://ci.syzbot.org/findings/4102267c-e678-4ffc-9ac0-4fb2dcbe5c0d/syz_repro

BUG: sleeping function called from invalid context at ./include/linux/sched/mm.h:323
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5856, name: syz.0.17
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
INFO: lockdep is turned off.
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 0 UID: 0 PID: 5856 Comm: syz.0.17 Tainted: G W syzkaller #0 PREEMPT(full)

Tainted: [W]=WARN
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014

Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
__might_resched+0x378/0x4d0 kernel/sched/core.c:9193
might_alloc include/linux/sched/mm.h:323 [inline]
slab_pre_alloc_hook mm/slub.c:4559 [inline]
slab_alloc_node mm/slub.c:4916 [inline]
__kmalloc_cache_noprof+0x74/0x660 mm/slub.c:5446
_kmalloc_noprof include/linux/slab.h:969 [inline]
_kzalloc_noprof include/linux/slab.h:1286 [inline]
configfs_get_super_info+0x218/0x5e0 fs/configfs/mount.c:91
configfs_get_tree+0x41/0xd0 fs/configfs/mount.c:170
vfs_get_tree+0x92/0x2a0 fs/super.c:1694
vfs_cmd_create+0xa2/0x200 fs/fsopen.c:231
__do_sys_fsconfig fs/fsopen.c:463 [inline]
__se_sys_fsconfig+0x6b9/0x810 fs/fsopen.c:350
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f5c9db9ce59

Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007f5c9ea71028 EFLAGS: 00000246 ORIG_RAX: 00000000000001af
RAX: ffffffffffffffda RBX: 00007f5c9de15fa0 RCX: 00007f5c9db9ce59
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000003
RBP: 00007f5c9dc32e6f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f5c9de16038 R14: 00007f5c9de15fa0 R15: 00007ffe63465d98
</TASK>

***

If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syz...@syzkaller.appspotmail.com

---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzk...@googlegroups.com.

To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).

The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.

The email will later be sent to:

[a.hin...@kernel.org bra...@kernel.org ha...@kernel.org h...@lst.de ja...@suse.cz k...@nvidia.com lei...@debian.org linux-...@vger.kernel.org linux-...@vger.kernel.org linux...@lists.infradead.org sa...@grimberg.me vi...@zeniv.linux.org.uk]

[Aleksandr Nogikh]

#syz upstream

> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-m...@googlegroups.com.

> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6a3a996f.52ae72c2.136ac7.0008.GAE%40google.com.