mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: syzbot <syzbot@kernel.org>,
	Krystian Kaniewski <krystianmkaniewski@gmail.com>,
	Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
	syzkaller-bugs@googlegroups.com, ocfs2-devel@lists.linux.dev,
	linux-kernel@vger.kernel.org, syzbot@lists.linux.dev
Subject: Re: [PATCH] ocfs2: fix circular locking dependency in ocfs2_init_acl()
Date: Tue, 4 Aug 2026 16:46:01 -0700	[thread overview]
Message-ID: <20260804164601.2a5f2a95f53f62b43a50e601@linux-foundation.org> (raw)
In-Reply-To: <f98ff905-74bf-4017-a673-fd28f30f11d3@linux.alibaba.com>

On Tue, 4 Aug 2026 14:36:02 +0800 Joseph Qi <joseph.qi@linux.alibaba.com> wrote:

> > Additionally, remove the `ip_xattr_sem` acquisition from
> > `ocfs2_xattr_set_handle()`. This function is only used while initializing a
> > new inode that has not yet been inserted into the inode hash or attached to
> > a dentry, meaning there is no risk of concurrent access and the lock is
> > unnecessary.
> > 
> > Fixes: 16c8d569f570 ("ocfs2/acl: use 'ip_xattr_sem' to protect getting extended attribute")
> > Assisted-by: Gemini:gemini-3.5-flash Gemini:gemini-3.1-pro-preview syzbot
> > Reported-by: syzbot+4007ab5229e732466d9f@syzkaller.appspotmail.com
> > Closes: https://syzkaller.appspot.com/bug?extid=4007ab5229e732466d9f
> > Link: https://syzkaller.appspot.com/ai_job?id=cc75363d-c672-499e-8fc5-44bcdc1cee39
> > Signed-off-by: Krystian Kaniewski <krystianmkaniewski@gmail.com>
> 
> Reviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>

Thanks.  AI review might have found a pre-existing bug:
	https://sashiko.dev/#/patchset/4094de06-9b69-4174-b2ee-08126dffc693@mail.kernel.org

      reply	other threads:[~2026-08-04 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30  7:42 syzbot
2026-08-04  6:36 ` Joseph Qi
2026-08-04 23:46   ` Andrew Morton [this message]

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=20260804164601.2a5f2a95f53f62b43a50e601@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=krystianmkaniewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=syzbot@kernel.org \
    --cc=syzbot@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®