[fs?] WARNING in vfs_setxattr (2)

5 views
Skip to first unread message

syzbot

unread,
Jun 19, 2023, 11:24:48 AM6/19/23
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: f86b85033b8c Merge branch 'for-next/core', remote-tracking..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=14bd4673280000
kernel config: https://syzkaller.appspot.com/x/.config?x=8776b67768a3c9af
dashboard link: https://syzkaller.appspot.com/bug?extid=7e82f8f7859824b9caea
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [bra...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/04ce092481c3/disk-f86b8503.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3f7f34b14d4e/vmlinux-f86b8503.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6f74fbca759a/Image-f86b8503.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff00011890a0b0, owner = 0x0, curr 0xffff000119651bc0, list empty
WARNING: CPU: 1 PID: 11370 at kernel/locking/rwsem.c:1370 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 1 PID: 11370 at kernel/locking/rwsem.c:1370 up_write+0x524/0x760 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 11370 Comm: syz-executor.4 Not tainted 6.4.0-rc5-syzkaller-gf86b85033b8c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1369 [inline]
pc : up_write+0x524/0x760 kernel/locking/rwsem.c:1626
lr : __up_write kernel/locking/rwsem.c:1369 [inline]
lr : up_write+0x524/0x760 kernel/locking/rwsem.c:1626
sp : ffff8000a47d7880
x29: ffff8000a47d7900 x28: 0000000000000000 x27: 1fffe00023121423
x26: dfff800000000000 x25: 1fffe00023121417 x24: ffff00011890a108
x23: 0000000000000000 x22: 0000000000000000 x21: ffff000119651bc0
x20: ffff00011890a0b0 x19: ffff00011890a0b0 x18: 1fffe00036848bc6
x17: ffff80008debd000 x16: ffff8000803122b8 x15: 0000000000000002
x14: 1ffff00011bd80ac x13: dfff800000000000 x12: 0000000000000003
x11: 0000000000000001 x10: 0000000000000003 x9 : 7f9f5785af123f00
x8 : 7f9f5785af123f00 x7 : ffff80008028cadc x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000007 x1 : ffff80008a59de40 x0 : ffff80012643a000
Call trace:
__up_write kernel/locking/rwsem.c:1369 [inline]
up_write+0x524/0x760 kernel/locking/rwsem.c:1626
inode_unlock include/linux/fs.h:780 [inline]
vfs_setxattr+0x1b4/0x344 fs/xattr.c:324
do_setxattr fs/xattr.c:630 [inline]
setxattr+0x208/0x29c fs/xattr.c:653
path_setxattr+0x17c/0x258 fs/xattr.c:672
__do_sys_setxattr fs/xattr.c:688 [inline]
__se_sys_setxattr fs/xattr.c:684 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:684
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x244 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:191
el0_svc+0x4c/0x160 arch/arm64/kernel/entry-common.c:647
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:665
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591
irq event stamp: 280
hardirqs last enabled at (279): [<ffff80008028cb7c>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1378 [inline]
hardirqs last enabled at (279): [<ffff80008028cb7c>] finish_lock_switch+0xbc/0x1e4 kernel/sched/core.c:5095
hardirqs last disabled at (280): [<ffff80008a437a04>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:407
softirqs last enabled at (170): [<ffff8000800218ec>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (170): [<ffff8000800218ec>] __do_softirq+0xac0/0xd54 kernel/softirq.c:600
softirqs last disabled at (143): [<ffff80008002b660>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:80
---[ 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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Sep 13, 2023, 11:16:01 AM9/13/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages