[v6.1] WARNING in current_check_refer_path

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7ec6f9fa3d97 Linux 6.1.114
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17fb9540580000
kernel config: https://syzkaller.appspot.com/x/.config?x=344cdb747ab79921
dashboard link: https://syzkaller.appspot.com/bug?extid=757256b24eb5b59ef116
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/e7551ab2b38b/disk-7ec6f9fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99ca69a69b01/vmlinux-7ec6f9fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0d62742f11c2/Image-7ec6f9fa.gz.xz

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

NILFS (loop3): broken superblock, retrying with spare superblock (blocksize = 1024)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5046 at security/landlock/fs.c:687 current_check_refer_path+0x274/0x914 security/landlock/fs.c:841
Modules linked in:
CPU: 0 PID: 5046 Comm: syz.3.229 Not tainted 6.1.114-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 : current_check_refer_path+0x274/0x914 security/landlock/fs.c:841
lr : get_mode_access security/landlock/fs.c:669 [inline]
lr : current_check_refer_path+0x270/0x914 security/landlock/fs.c:841
sp : ffff800021967820
x29: ffff800021967960 x28: 000000000000ffff x27: 1fffe0001e39d4bc
x26: 0000000000000001 x25: 0000000000000001 x24: 0000000000000000
x23: ffff0000f1cea5e0 x22: ffff70000432cf10 x21: ffff0000dbd552a8
x20: dfff800000000000 x19: ffff0000dbd55200 x18: ffff800021967020
x17: 0000000000000000 x16: ffff8000121deac0 x15: 0000000000000002
x14: 1ffff00002b3a0b0 x13: dfff800000000000 x12: 0000000000040000
x11: 000000000001cc94 x10: ffff8000226db000 x9 : ffff80000a787a6c
x8 : 000000000001cc95 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000010
x2 : 000000000000000c x1 : 000000000000ffff x0 : 000000000000d000
Call trace:
current_check_refer_path+0x274/0x914 security/landlock/fs.c:841
hook_path_rename+0x4c/0x60 security/landlock/fs.c:1113
security_path_rename+0x154/0x1f0 security/security.c:1217
do_renameat2+0x754/0xe64 fs/namei.c:5014
__do_sys_renameat2 fs/namei.c:5060 [inline]
__se_sys_renameat2 fs/namei.c:5057 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5057
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 8316
hardirqs last enabled at (8315): [<ffff800008343af4>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (8316): [<ffff80001228c9f4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (8172): [<ffff8000081c7c58>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (8172): [<ffff8000081c7c58>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:599
softirqs last disabled at (8133): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:605
---[ end trace 0000000000000000 ]---


---
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: 7ec6f9fa3d97 Linux 6.1.114
git tree: linux-6.1.y

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

kernel config: https://syzkaller.appspot.com/x/.config?x=344cdb747ab79921
dashboard link: https://syzkaller.appspot.com/bug?extid=757256b24eb5b59ef116
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=1608e55f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=101f52a7980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e7551ab2b38b/disk-7ec6f9fa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/99ca69a69b01/vmlinux-7ec6f9fa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0d62742f11c2/Image-7ec6f9fa.gz.xz

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

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

NILFS (loop0): broken superblock, retrying with spare superblock (blocksize = 1024)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4290 at security/landlock/fs.c:687 current_check_refer_path+0x274/0x914 security/landlock/fs.c:841
Modules linked in:
CPU: 0 PID: 4290 Comm: syz-executor257 Not tainted 6.1.114-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 : current_check_refer_path+0x274/0x914 security/landlock/fs.c:841
lr : get_mode_access security/landlock/fs.c:669 [inline]
lr : current_check_refer_path+0x270/0x914 security/landlock/fs.c:841

sp : ffff800020f97820
x29: ffff800020f97960 x28: 000000000000ffff x27: 1fffe0001be90ef0

x26: 0000000000000001 x25: 0000000000000001 x24: 0000000000000000

x23: ffff0000df487780 x22: ffff7000041f2f10 x21: ffff0000d1424ca8
x20: dfff800000000000 x19: ffff0000d1424c00 x18: ffff800020f96d60
x17: 0000000000000000 x16: ffff8000121deac0 x15: 0000000000000000
x14: 1ffff00002b3a0b0 x13: dfff800000000000 x12: ffff7000041f2f23
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff80000a787a6c
x8 : ffff0000de91d340 x7 : 0000000000000000 x6 : 0000000000000000

x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000010
x2 : 000000000000000c x1 : 000000000000ffff x0 : 000000000000d000
Call trace:
current_check_refer_path+0x274/0x914 security/landlock/fs.c:841
hook_path_rename+0x4c/0x60 security/landlock/fs.c:1113
security_path_rename+0x154/0x1f0 security/security.c:1217
do_renameat2+0x754/0xe64 fs/namei.c:5014
__do_sys_renameat2 fs/namei.c:5060 [inline]
__se_sys_renameat2 fs/namei.c:5057 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5057
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

irq event stamp: 21736
hardirqs last enabled at (21735): [<ffff800008343af4>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:261
hardirqs last disabled at (21736): [<ffff80001228c9f4>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (21146): [<ffff8000081c7c58>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (21146): [<ffff8000081c7c58>] handle_softirqs+0xb84/0xd58 kernel/softirq.c:599
softirqs last disabled at (21091): [<ffff800008020174>] __do_softirq+0x14/0x20 kernel/softirq.c:605

---[ end trace 0000000000000000 ]---


---

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.