[v5.15] WARNING in hook_path_rename

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 74cdd62cb470 Linux 5.15.169
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13a42630580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a532e68091e668cf
dashboard link: https://syzkaller.appspot.com/bug?extid=e26c000b9284837a3bc7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9cd5ba5c8eb5/disk-74cdd62c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/51345e3be25c/vmlinux-74cdd62c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9670d8303340/Image-74cdd62c.gz.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 7488 at security/landlock/fs.c:576 hook_path_rename+0x200/0x2fc security/landlock/fs.c:637
Modules linked in:
CPU: 0 PID: 7488 Comm: syz.0.1135 Not tainted 5.15.169-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hook_path_rename+0x200/0x2fc security/landlock/fs.c:637
lr : get_mode_access security/landlock/fs.c:558 [inline]
lr : hook_path_rename+0x1fc/0x2fc security/landlock/fs.c:637
sp : ffff8000207a7980
x29: ffff8000207a7980 x28: ffff8000207a7c60 x27: dfff800000000000
x26: ffff8000207a7c00 x25: dfff800000000000 x24: 0000000000000020
x23: 0000000000000020 x22: 0000000000000020 x21: 000000000000ffff
x20: ffff0000d41c8800 x19: ffff8000207a7c00 x18: 0000000000000001
x17: 0000000000000002 x16: ffff80000824ebd0 x15: 00000000ffffffff
x14: 1ffff0000295606a x13: dfff800000000000 x12: 0000000000040000
x11: 0000000000008418 x10: ffff800020c3a000 x9 : 0000000000008419
x8 : 0000000000000000 x7 : ffff8000089e3664 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000002 x3 : ffff0000c52dd490
x2 : ffff8000207a7be0 x1 : 000000000000ffff x0 : 000000000000d000
Call trace:
hook_path_rename+0x200/0x2fc security/landlock/fs.c:637
security_path_rename+0x168/0x274 security/security.c:1199
do_renameat2+0x75c/0x10c0 fs/namei.c:4972
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 7568
hardirqs last enabled at (7567): [<ffff80000832c128>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (7568): [<ffff800011ab3ab0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (7488): [<ffff8000080308b0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (7486): [<ffff80000803087c>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace 42eb39382fefc929 ]---


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 74cdd62cb470 Linux 5.15.169
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=12862630580000

kernel config: https://syzkaller.appspot.com/x/.config?x=a532e68091e668cf
dashboard link: https://syzkaller.appspot.com/bug?extid=e26c000b9284837a3bc7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16862630580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1295c6f7980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9cd5ba5c8eb5/disk-74cdd62c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/51345e3be25c/vmlinux-74cdd62c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9670d8303340/Image-74cdd62c.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/c4cf6161175f/mount_0.gz

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

NILFS (loop0): broken superblock, retrying with spare superblock (blocksize = 1024)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4019 at security/landlock/fs.c:576 hook_path_rename+0x200/0x2fc security/landlock/fs.c:637
Modules linked in:
CPU: 0 PID: 4019 Comm: syz-executor190 Not tainted 5.15.169-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hook_path_rename+0x200/0x2fc security/landlock/fs.c:637
lr : get_mode_access security/landlock/fs.c:558 [inline]
lr : hook_path_rename+0x1fc/0x2fc security/landlock/fs.c:637

sp : ffff80001d0c7980
x29: ffff80001d0c7980 x28: ffff80001d0c7c60 x27: dfff800000000000
x26: ffff80001d0c7c00 x25: dfff800000000000 x24: 0000000000000020

x23: 0000000000000020 x22: 0000000000000020 x21: 000000000000ffff

x20: ffff0000cb754400 x19: ffff80001d0c7c00 x18: 0000000000000001
x17: 0000000000000000 x16: ffff80000824ebd0 x15: 00000000ffffffff
x14: 1ffff0000295606a x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000cae7b680

x8 : 0000000000000000 x7 : ffff8000089e3664 x6 : 0000000000000000

x5 : 0000000000000000 x4 : 0000000000000002 x3 : ffff0000dc118d38
x2 : ffff80001d0c7be0 x1 : 000000000000ffff x0 : 000000000000d000

Call trace:
hook_path_rename+0x200/0x2fc security/landlock/fs.c:637
security_path_rename+0x168/0x274 security/security.c:1199
do_renameat2+0x75c/0x10c0 fs/namei.c:4972
__do_sys_renameat2 fs/namei.c:5018 [inline]
__se_sys_renameat2 fs/namei.c:5015 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

irq event stamp: 20358
hardirqs last enabled at (20357): [<ffff80000832c128>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (20358): [<ffff800011ab3ab0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (19676): [<ffff8000080308b0>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (19674): [<ffff80000803087c>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace e2b5690d2597da1f ]---


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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.