All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 08 Nov 2025 21:17:01 -0800	[thread overview]
Message-ID: <691023cd.a70a0220.22f260.009d.GAE@google.com> (raw)
In-Reply-To: <20251109050218.648149-1-kartikey406@gmail.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in chown_common

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff88804066a898, owner = 0x0, curr 0xffff88803347c900, list empty
WARNING: CPU: 0 PID: 5867 at kernel/locking/rwsem.c:1381 __up_write kernel/locking/rwsem.c:1380 [inline]
WARNING: CPU: 0 PID: 5867 at kernel/locking/rwsem.c:1381 up_write+0x3a2/0x420 kernel/locking/rwsem.c:1643
Modules linked in:
CPU: 0 UID: 0 PID: 5867 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 20 ff 6a 8b 48 c7 c6 40 01 6b 8b 48 8b 14 24 4c 89 f1 4d 89 e0 4c 8b 4c 24 08 41 52 e8 c3 35 e6 ff 48 83 c4 08 90 <0f> 0b 90 90 e9 6d fd ff ff 48 c7 c1 94 33 7d 8f 80 e1 07 80 c1 03
RSP: 0018:ffffc9000ceafc30 EFLAGS: 00010296
RAX: a13d96110bebcb00 RBX: ffff88804066a898 RCX: ffff88803347c900
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: dffffc0000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1bba684 R12: 0000000000000000
R13: ffff88804066a8f0 R14: ffff88804066a898 R15: 1ffff110080cd514
FS:  00007f07520966c0(0000) GS:ffff88808d730000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 000000004e9f3000 CR4: 0000000000352ef0
Call Trace:
 <TASK>
 inode_unlock include/linux/fs.h:990 [inline]
 chown_common+0x3f1/0x5b0 fs/open.c:801
 do_fchownat+0x161/0x270 fs/open.c:833
 __do_sys_fchownat fs/open.c:848 [inline]
 __se_sys_fchownat fs/open.c:845 [inline]
 __x64_sys_fchownat+0xb5/0xd0 fs/open.c:845
 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:0x7f075118efc9
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:00007f0752096038 EFLAGS: 00000246 ORIG_RAX: 0000000000000104
RAX: ffffffffffffffda RBX: 00007f07513e6090 RCX: 00007f075118efc9
RDX: 0000000000000000 RSI: 0000200000000000 RDI: ffffffffffffff9c
RBP: 00007f0751211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f07513e6128 R14: 00007f07513e6090 R15: 00007ffd9054c3d8
 </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=133c6a92580000
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=140c8412580000


       reply	other threads:[~2025-11-09  5:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251109050218.648149-1-kartikey406@gmail.com>
2025-11-09  5:17 ` 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] <20251109142934.1142273-1-kartikey406@gmail.com>
2025-11-09 15:05 ` 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] <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=691023cd.a70a0220.22f260.009d.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.