From: syzbot <syzbot+04c2672c56fbb9401640@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] WARNING in chown_common
Date: Sun, 09 Nov 2025 07:05:02 -0800 [thread overview]
Message-ID: <6910ad9e.a70a0220.22f260.00ba.GAE@google.com> (raw)
In-Reply-To: <20251109142934.1142273-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: About to unlock rwsem we don't own!
After notify_change: owner=0, error=0
BUG: About to unlock rwsem we don't own!
inode=ffff888043102e60
i_rwsem.owner=0
current=ffff88801fbd8000
delegated_inode=0000000000000000
CPU: 0 UID: 0 PID: 5829 Comm: syz.0.21 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
<TASK>
dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
chown_common+0x555/0x6f0 fs/open.c:803
do_fchownat+0x161/0x270 fs/open.c:834
__do_sys_fchownat fs/open.c:849 [inline]
__se_sys_fchownat fs/open.c:846 [inline]
__x64_sys_fchownat+0xb5/0xd0 fs/open.c:846
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7f3658efc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7f373a1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000104
RAX: ffffffffffffffda RBX: 00007f7f367e6090 RCX: 00007f7f3658efc9
RDX: 0000000000000000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f7f36611f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7f367e6128 R14: 00007f7f367e6090 R15: 00007fff1e869178
</TASK>
inode_unlock: inode=ffff888043102e60, owner=0, current=ffff88801fbd8000 (syz.0.21:5829)
CPU: 0 UID: 0 PID: 5829 Comm: syz.0.21 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
Call Trace:
<TASK>
dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
inode_unlock+0x92/0xd0 include/linux/fs.h:994
chown_common+0x55f/0x6f0 fs/open.c:805
do_fchownat+0x161/0x270 fs/open.c:834
__do_sys_fchownat fs/open.c:849 [inline]
__se_sys_fchownat fs/open.c:846 [inline]
__x64_sys_fchownat+0xb5/0xd0 fs/open.c:846
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7f3658efc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7f373a1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000104
RAX: ffffffffffffffda RBX: 00007f7f367e6090 RCX: 00007f7f3658efc9
RDX: 0000000000000000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f7f36611f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7f367e6128 R14: 00007f7f367e6090 R15: 00007fff1e869178
</TASK>
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888043102f38, owner = 0x0, curr 0xffff88801fbd8000, list empty
WARNING: CPU: 0 PID: 5829 at kernel/locking/rwsem.c:1381 __up_write kernel/locking/rwsem.c:1380 [inline]
WARNING: CPU: 0 PID: 5829 at kernel/locking/rwsem.c:1381 up_write+0x3a2/0x420 kernel/locking/rwsem.c:1643
Modules linked in:
CPU: 0 UID: 0 PID: 5829 Comm: syz.0.21 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:__up_write kernel/locking/rwsem.c:1380 [inline]
RIP: 0010:up_write+0x3a2/0x420 kernel/locking/rwsem.c:1643
Code: d0 48 c7 c7 80 ff 6a 8b 48 c7 c6 a0 01 6b 8b 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 b3 35 e6 ff 48 83 c4 08 90 <0f> 0b 90 90 e9 6d fd ff ff 48 c7 c1 94 55 7d 8f 80 e1 07 80 c1 03
RSP: 0018:ffffc90002e77bf0 EFLAGS: 00010296
RAX: 59e03a60efe32100 RBX: ffff888043102f38 RCX: ffff88801fbd8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: dffffc0000000000 R08: ffffffff8f7d2577 R09: 1ffffffff1efa4ae
R10: dffffc0000000000 R11: fffffbfff1efa4af R12: 0000000000000000
R13: ffff888043102f90 R14: ffff888043102f38 R15: 1ffff110086205e8
FS: 00007f7f373a16c0(0000) GS:ffff88808d729000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000043752000 CR4: 0000000000352ef0
Call Trace:
<TASK>
chown_common+0x55f/0x6f0 fs/open.c:805
do_fchownat+0x161/0x270 fs/open.c:834
__do_sys_fchownat fs/open.c:849 [inline]
__se_sys_fchownat fs/open.c:846 [inline]
__x64_sys_fchownat+0xb5/0xd0 fs/open.c:846
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7f3658efc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7f373a1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000104
RAX: ffffffffffffffda RBX: 00007f7f367e6090 RCX: 00007f7f3658efc9
RDX: 0000000000000000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f7f36611f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7f367e6128 R14: 00007f7f367e6090 R15: 00007fff1e869178
</TASK>
Tested on:
commit: 439fc29d Merge tag 'drm-fixes-2025-11-09' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15f21a58580000
kernel config: https://syzkaller.appspot.com/x/.config?x=929790bc044e87d7
dashboard link: https://syzkaller.appspot.com/bug?extid=04c2672c56fbb9401640
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1624d0b4580000
next parent reply other threads:[~2025-11-09 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251109142934.1142273-1-kartikey406@gmail.com>
2025-11-09 15:05 ` syzbot [this message]
[not found] <20251109151559.1145822-1-kartikey406@gmail.com>
2025-11-09 15:32 ` [syzbot] [gfs2?] WARNING in chown_common syzbot
[not found] <20251109132736.1141174-1-kartikey406@gmail.com>
2025-11-09 13:29 ` syzbot
[not found] <20251109122513.1139397-1-kartikey406@gmail.com>
2025-11-09 13:02 ` syzbot
[not found] <20251109115742.1138274-1-kartikey406@gmail.com>
2025-11-09 12:14 ` syzbot
[not found] <20251109114011.1100867-1-kartikey406@gmail.com>
2025-11-09 11:56 ` syzbot
[not found] <20251109090808.839886-1-kartikey406@gmail.com>
2025-11-09 9:30 ` syzbot
[not found] <20251109050218.648149-1-kartikey406@gmail.com>
2025-11-09 5:17 ` syzbot
[not found] <CAMz+-CPDh3FF3Fso8UjYyd0=uyV2hJvYQLTVracNyo896rsF1A@mail.gmail.com>
2025-10-29 10:53 ` syzbot
[not found] <20251017085719.821125-1-kartikey406@gmail.com>
2025-10-17 9:20 ` syzbot
2025-10-12 5:45 syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6910ad9e.a70a0220.22f260.00ba.GAE@google.com \
--to=syzbot+04c2672c56fbb9401640@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.