mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Diogo Jahchan Koike <djahchankoike@gmail.com>
Cc: Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
	Joseph Qi <joseph.qi@linux.alibaba.com>,
	syzbot+1fed2de07d8e11a3ec1b@syzkaller.appspotmail.com,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ocfs2: fix lock acquisition order in refcounttree
Date: Sat, 25 Apr 2026 14:26:35 -0700	[thread overview]
Message-ID: <20260425142635.2ad0300d02ddea1bed94d6e2@linux-foundation.org> (raw)
In-Reply-To: <20250714221552.4853-1-djahchankoike@gmail.com>

On Mon, 14 Jul 2025 19:15:32 -0300 Diogo Jahchan Koike <djahchankoike@gmail.com> wrote:

> Acquiring the locks in refcounttree should follow
> the ip_alloc --> ip_xattr ordering, as done by multiple
> code paths in ocfs2; otherwise, we risk an ABBA deadlock
> (i.e in the start transaction path).
> 
> Reported-by: syzbot+1fed2de07d8e11a3ec1b@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=1fed2de07d8e11a3ec1b

But ocfs2_reflink() does

	down_write(&OCFS2_I(inode)->ip_xattr_sem);
	down_write(&OCFS2_I(inode)->ip_alloc_sem);



  parent reply	other threads:[~2026-04-25 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 22:15 Diogo Jahchan Koike
2025-07-15  2:51 ` Tetsuo Handa
2025-07-18 13:54   ` Tetsuo Handa
2025-07-21 10:40     ` Tetsuo Handa
2026-04-25 21:26 ` Andrew Morton [this message]
2026-04-25 22:30   ` Tetsuo Handa

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=20260425142635.2ad0300d02ddea1bed94d6e2@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=djahchankoike@gmail.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=syzbot+1fed2de07d8e11a3ec1b@syzkaller.appspotmail.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®