From: syzbot <syzbot+293a57918b36cfae3d48@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (3)
Date: Fri, 17 Jul 2026 03:36:02 -0700 [thread overview]
Message-ID: <6a5a0592.42649fcc.6186.0003.GAE@google.com> (raw)
In-Reply-To: <20260717091456.36085-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING: lock held when returning to user space in ext4_write_inline_data_end
loop0: detected capacity change from 0 to 1024
================================================
WARNING: lock held when returning to user space!
syzkaller #0 Not tainted
------------------------------------------------
syz.0.999/10153 is leaving the kernel with locks still held!
1 lock held by syz.0.999/10153:
#0: ffff0000e0bc67e0 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_lock_xattr fs/ext4/xattr.h:157 [inline]
#0: ffff0000e0bc67e0 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_inline_data_end+0x198/0x9f8 fs/ext4/inline.c:814
Tested on:
commit: a13c140c Linux 7.2-rc3
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=1730b4b9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ecdef466b08b9772
dashboard link: https://syzkaller.appspot.com/bug?extid=293a57918b36cfae3d48
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=134f6789580000
next parent reply other threads:[~2026-07-17 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260717091456.36085-1-kartikey406@gmail.com>
2026-07-17 10:36 ` syzbot [this message]
[not found] <20260717134133.38390-1-kartikey406@gmail.com>
2026-07-17 14:48 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (3) syzbot
[not found] <20260717105327.37079-1-kartikey406@gmail.com>
2026-07-17 11:57 ` syzbot
[not found] <20260717000803.14708-1-kartikey406@gmail.com>
2026-07-17 4:39 ` syzbot
2026-07-16 7:50 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=6a5a0592.42649fcc.6186.0003.GAE@google.com \
--to=syzbot+293a57918b36cfae3d48@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.