All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com>
To: albinbabuvarghese20@gmail.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref
Date: Wed, 17 Sep 2025 21:20:02 -0700	[thread overview]
Message-ID: <68cb8872.050a0220.2ff435.05a2.GAE@google.com> (raw)
In-Reply-To: <CADfthj0NZ7duGqudQRUfmE=J69+hBkb+gWKQMVrJ18hDsMUGpw@mail.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_xattr_inode_update_ref

EXT4-fs (loop0): 1 orphan inode deleted
EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 ro without journal. Quota mode: none.
================================================
WARNING: lock held when returning to user space!
syzkaller #0 Not tainted
------------------------------------------------
syz.0.17/6582 is leaving the kernel with locks still held!
1 lock held by syz.0.17/6582:
 #0: ffff88805849d798 (&sb->s_type->i_mutex_key#8/3){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:915 [inline]
 #0: ffff88805849d798 (&sb->s_type->i_mutex_key#8/3){+.+.}-{4:4}, at: ext4_xattr_inode_update_ref+0xad/0x650 fs/ext4/xattr.c:1025


Tested on:

commit:         592a93fe Merge tag '6.17-rc6-ksmbd-fixes' of git://git..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13caef62580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f5b21423ca3f0a96
dashboard link: https://syzkaller.appspot.com/bug?extid=0be4f339a8218d2a5bb1
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=14c58712580000


       reply	other threads:[~2025-09-18  4:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADfthj0NZ7duGqudQRUfmE=J69+hBkb+gWKQMVrJ18hDsMUGpw@mail.gmail.com>
2025-09-18  4:20 ` syzbot [this message]
     [not found] <CAHxJ8O_w8ewga16ORMaoM8MZj_pbh02ZRV1T_z1B6i8Q=9AE6g@mail.gmail.com>
2025-09-24 19:56 ` [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref syzbot
     [not found] <CAHxJ8O9EHnwSkBNOmBOEg3GvDxcnqsQ5cURd+uG8G2EvUcXYfg@mail.gmail.com>
2025-09-19 23:56 ` syzbot
     [not found] <CADfthj3f-mmvvm3tAWLUmtZGTKw46+eqxZhPekLA_eKLgOUG2g@mail.gmail.com>
2025-09-18  5:19 ` syzbot
     [not found] <CAHxJ8O_F5ssDpCPi48eHRY=q29odqrjnOxfvdoOd5xppdhht7A@mail.gmail.com>
2025-09-18  1:28 ` syzbot
2025-09-11  0:08 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=68cb8872.050a0220.2ff435.05a2.GAE@google.com \
    --to=syzbot+0be4f339a8218d2a5bb1@syzkaller.appspotmail.com \
    --cc=albinbabuvarghese20@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.