[v5.15] possible deadlock in mi_read

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2ddbd0f967b3 Linux 5.15.102
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=156c7cecc80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fec083380faceb1e
dashboard link: https://syzkaller.appspot.com/bug?extid=de116336948b785c6555
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156d2aa91f3c/disk-2ddbd0f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0e97f5be5fb/vmlinux-2ddbd0f9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20d0a55a041d/bzImage-2ddbd0f9.xz

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

============================================
WARNING: possible recursive locking detected
5.15.102-syzkaller #0 Not tainted
--------------------------------------------
syz-executor.4/6088 is trying to acquire lock:
ffff88809ae14360 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
ffff88809ae14360 (&ni->ni_lock/4){+.+.}-{3:3}, at: mi_read+0x2f2/0x560 fs/ntfs3/record.c:148

but task is already holding lock:
ffff8880302e2d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
ffff8880302e2d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf5/0x190 fs/ntfs3/namei.c:82

other info that might help us debug this:
Possible unsafe locking scenario:

CPU0
----
lock(&ni->ni_lock/4);
lock(&ni->ni_lock/4);

*** DEADLOCK ***

May be due to missing lock nesting notation

2 locks held by syz-executor.4/6088:
#0: ffff8880302e2fe0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
#0: ffff8880302e2fe0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: open_last_lookups fs/namei.c:3403 [inline]
#0: ffff8880302e2fe0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: path_openat+0x809/0x2ee0 fs/namei.c:3612
#1: ffff8880302e2d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
#1: ffff8880302e2d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf5/0x190 fs/ntfs3/namei.c:82

stack backtrace:
CPU: 0 PID: 6088 Comm: syz-executor.4 Not tainted 5.15.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_deadlock_bug kernel/locking/lockdep.c:2946 [inline]
check_deadlock kernel/locking/lockdep.c:2989 [inline]
validate_chain+0x46cf/0x58b0 kernel/locking/lockdep.c:3774
__lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5011
lock_acquire+0x1ff/0x570 kernel/locking/lockdep.c:5622
__mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
mi_read+0x2f2/0x560 fs/ntfs3/record.c:148
ntfs_read_mft fs/ntfs3/inode.c:69 [inline]
ntfs_iget5+0x44c/0x3760 fs/ntfs3/inode.c:517
dir_search_u+0x2f6/0x390 fs/ntfs3/dir.c:264
ntfs_lookup+0x102/0x190 fs/ntfs3/namei.c:83
lookup_open fs/namei.c:3312 [inline]
open_last_lookups fs/namei.c:3404 [inline]
path_openat+0x10d2/0x2ee0 fs/namei.c:3612
do_filp_open+0x21c/0x460 fs/namei.c:3642
do_sys_openat2+0x13b/0x500 fs/open.c:1211
do_sys_open fs/open.c:1227 [inline]
__do_sys_open fs/open.c:1235 [inline]
__se_sys_open fs/open.c:1231 [inline]
__x64_sys_open+0x221/0x270 fs/open.c:1231
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f93ef5460f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f93e5897168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f93ef666050 RCX: 00007f93ef5460f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000080
RBP: 00007f93ef5a1ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd8e82a3df R14: 00007f93e5897300 R15: 0000000000022000
</TASK>


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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6449a0ba6843 Linux 6.1.19
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11308e76c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=9ed8b3ec03e8c126
dashboard link: https://syzkaller.appspot.com/bug?extid=e734ffa9b17a318863d2

compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/0ad616da3180/disk-6449a0ba.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/42677a30acb3/vmlinux-6449a0ba.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2e21fe35d03d/bzImage-6449a0ba.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+e734ff...@syzkaller.appspotmail.com

============================================
WARNING: possible recursive locking detected

6.1.19-syzkaller #0 Not tainted
--------------------------------------------
syz-executor.5/28098 is trying to acquire lock:
ffff88802c92c360 (&ni->ni_lock/4){+.+.}-{3:3}
, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]

, at: mi_read+0x2f2/0x560 fs/ntfs3/record.c:148

but task is already holding lock:

ffff88802c928fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]
ffff88802c928fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf5/0x190 fs/ntfs3/namei.c:82

other info that might help us debug this:
Possible unsafe locking scenario:

CPU0
----
lock(&ni->ni_lock/4);
lock(&ni->ni_lock/4);

*** DEADLOCK ***

May be due to missing lock nesting notation

2 locks held by syz-executor.5/28098:
#0: ffff88802c929260 (&type->i_mutex_dir_key#13){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:766 [inline]
#0: ffff88802c929260 (&type->i_mutex_dir_key#13){++++}-{3:3}, at: open_last_lookups fs/namei.c:3480 [inline]
#0: ffff88802c929260 (&type->i_mutex_dir_key#13){++++}-{3:3}, at: path_openat+0x7a7/0x2e60 fs/namei.c:3711
#1: ffff88802c928fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]
#1: ffff88802c928fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf5/0x190 fs/ntfs3/namei.c:82

stack backtrace:
CPU: 0 PID: 28098 Comm: syz-executor.5 Not tainted 6.1.19-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106

print_deadlock_bug kernel/locking/lockdep.c:2991 [inline]
check_deadlock kernel/locking/lockdep.c:3034 [inline]
validate_chain+0x4726/0x58e0 kernel/locking/lockdep.c:3819
__lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
lock_acquire+0x23a/0x630 kernel/locking/lockdep.c:5669
__mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]

mi_read+0x2f2/0x560 fs/ntfs3/record.c:148
ntfs_read_mft fs/ntfs3/inode.c:69 [inline]

ntfs_iget5+0x453/0x3760 fs/ntfs3/inode.c:517

dir_search_u+0x2f6/0x390 fs/ntfs3/dir.c:264
ntfs_lookup+0x102/0x190 fs/ntfs3/namei.c:83

lookup_open fs/namei.c:3391 [inline]
open_last_lookups fs/namei.c:3481 [inline]
path_openat+0x10fb/0x2e60 fs/namei.c:3711
do_filp_open+0x230/0x480 fs/namei.c:3741
do_sys_openat2+0x13b/0x500 fs/open.c:1310
do_sys_open fs/open.c:1326 [inline]
__do_sys_open fs/open.c:1334 [inline]
__se_sys_open fs/open.c:1330 [inline]
__x64_sys_open+0x221/0x270 fs/open.c:1330

do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80

entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7daf48c0f9

Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007f7db01cf168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f7daf5abf80 RCX: 00007f7daf48c0f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000240
RBP: 00007f7daf4e7b39 R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

R13: 00007fffe8f314ef R14: 00007f7db01cf300 R15: 0000000000022000

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: ca48fc16c493 Linux 6.1.27
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14b5e212280000
kernel config: https://syzkaller.appspot.com/x/.config?x=aea4bb7802570997

dashboard link: https://syzkaller.appspot.com/bug?extid=e734ffa9b17a318863d2
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=103a8c4c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17876014280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ec11c1903c52/disk-ca48fc16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8ce41c1ad391/vmlinux-ca48fc16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/affba5631cad/Image-ca48fc16.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2401badf051a/mount_0.gz

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

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)

============================================
WARNING: possible recursive locking detected

6.1.27-syzkaller #0 Not tainted
--------------------------------------------
syz-executor107/4223 is trying to acquire lock:
ffff0000df9f1e80 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]
ffff0000df9f1e80 (&ni->ni_lock/4){+.+.}-{3:3}, at: mi_read+0x278/0x488 fs/ntfs3/record.c:148

but task is already holding lock:

ffff0000df9f6840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]
ffff0000df9f6840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf4/0x1a4 fs/ntfs3/namei.c:82

other info that might help us debug this:
Possible unsafe locking scenario:

CPU0
----
lock(&ni->ni_lock/4);
lock(&ni->ni_lock/4);

*** DEADLOCK ***

May be due to missing lock nesting notation

2 locks held by syz-executor107/4223:
#0: ffff0000df9f6ae0 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:766 [inline]
#0: ffff0000df9f6ae0 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1701
#1: ffff0000df9f6840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]
#1: ffff0000df9f6840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf4/0x1a4 fs/ntfs3/namei.c:82

stack backtrace:
CPU: 0 PID: 4223 Comm: syz-executor107 Not tainted 6.1.27-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
__lock_acquire+0x6310/0x764c kernel/locking/lockdep.c:5056
lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669
__mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799
ni_lock fs/ntfs3/ntfs_fs.h:1108 [inline]
mi_read+0x278/0x488 fs/ntfs3/record.c:148
ntfs_read_mft fs/ntfs3/inode.c:69 [inline]
ntfs_iget5+0x34c/0x2b38 fs/ntfs3/inode.c:517
dir_search_u+0x298/0x324 fs/ntfs3/dir.c:264
ntfs_lookup+0x104/0x1a4 fs/ntfs3/namei.c:83
__lookup_slow+0x250/0x374 fs/namei.c:1685
lookup_slow+0x60/0x84 fs/namei.c:1702
walk_component+0x280/0x36c fs/namei.c:1993
lookup_last fs/namei.c:2450 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2474
filename_lookup+0x1d4/0x4e0 fs/namei.c:2503
user_path_at_empty+0x5c/0x1a4 fs/namei.c:2876
user_path_at include/linux/namei.h:57 [inline]
path_setxattr+0xbc/0x258 fs/xattr.c:631
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648
__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:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
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:581


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

syzbot has found a reproducer for the following issue on:

HEAD commit: 8a7f2a5c5aa1 Linux 5.15.110
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11c824bc280000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e93d602da27af41

dashboard link: https://syzkaller.appspot.com/bug?extid=de116336948b785c6555
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1084e182280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1436a0b8280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/16bea75b636d/disk-8a7f2a5c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b169e33dcf2/vmlinux-8a7f2a5c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/190d08a00950/Image-8a7f2a5c.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/eb24693c131c/mount_0.gz

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

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)

============================================
WARNING: possible recursive locking detected

5.15.110-syzkaller #0 Not tainted
--------------------------------------------
syz-executor469/3963 is trying to acquire lock:
ffff0000dfc89e80 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
ffff0000dfc89e80 (&ni->ni_lock/4){+.+.}-{3:3}, at: mi_read+0x278/0x488 fs/ntfs3/record.c:148

but task is already holding lock:

ffff0000dfc8e840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
ffff0000dfc8e840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf4/0x1a4 fs/ntfs3/namei.c:82

other info that might help us debug this:
Possible unsafe locking scenario:

CPU0
----
lock(&ni->ni_lock/4);
lock(&ni->ni_lock/4);

*** DEADLOCK ***

May be due to missing lock nesting notation

2 locks held by syz-executor469/3963:
#0: ffff0000dfc8eae0 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
#0: ffff0000dfc8eae0 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1675
#1: ffff0000dfc8e840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
#1: ffff0000dfc8e840 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf4/0x1a4 fs/ntfs3/namei.c:82

stack backtrace:
CPU: 1 PID: 3963 Comm: syz-executor469 Not tainted 5.15.110-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216

__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106

dump_stack+0x1c/0x58 lib/dump_stack.c:113
__lock_acquire+0x62b4/0x7620 kernel/locking/lockdep.c:5011
lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5622
__mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
ni_lock fs/ntfs3/ntfs_fs.h:1107 [inline]
mi_read+0x278/0x488 fs/ntfs3/record.c:148
ntfs_read_mft fs/ntfs3/inode.c:69 [inline]
ntfs_iget5+0x344/0x2b30 fs/ntfs3/inode.c:517

dir_search_u+0x298/0x324 fs/ntfs3/dir.c:264
ntfs_lookup+0x104/0x1a4 fs/ntfs3/namei.c:83

__lookup_slow+0x250/0x388 fs/namei.c:1659
lookup_slow+0x60/0x84 fs/namei.c:1676
walk_component+0x394/0x4cc fs/namei.c:1972
lookup_last fs/namei.c:2427 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2451
filename_lookup+0x1c4/0x4c8 fs/namei.c:2480
user_path_at_empty+0x5c/0x1a4 fs/namei.c:2853
user_path_at include/linux/namei.h:57 [inline]
path_setxattr+0xbc/0x258 fs/xattr.c:625
__do_sys_setxattr fs/xattr.c:646 [inline]
__se_sys_setxattr fs/xattr.c:642 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:642
__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:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584