[moderation] [fs?] linux-next test error: BUG: sleeping function called from invalid context in corrupted

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0fc4bfab2cd4 Add linux-next specific files for 20240625
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1575153e980000
kernel config: https://syzkaller.appspot.com/x/.config?x=df444fac2868e4e3
dashboard link: https://syzkaller.appspot.com/bug?extid=7675182c3be4378eea06
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org linux...@vger.kernel.org s...@canb.auug.org.au vi...@zeniv.linux.org.uk]

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/66ca94996136/disk-0fc4bfab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c24a2abc9a2d/vmlinux-0fc4bfab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/05854f8c1865/bzImage-0fc4bfab.xz

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

BUG: sleeping function called from invalid context at include/linux/sched/mm.h:337
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5085, name: udevd
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
3 locks held by udevd/5085:
#0: ffff88802a55e420 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:409
#1: ffff888023f1eb48 (&type->i_mutex_dir_key#5/1){+.+.}-{3:3}, a


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