public inbox for linux-kernel-mentees@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Prithvi <activprithvi@gmail.com>
Cc: joseph.qi@linux.alibaba.com, mark@fasheh.com, jlbec@evilplan.org,
	heming.zhao@suse.com, ocfs2-devel@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
	david.hunter.linux@gmail.com, khalid@kernel.org
Subject: Re: [PATCH] ocfs2: Fix circular locking dependency in ocfs2_del_inode_from_orphan()
Date: Thu, 15 Jan 2026 04:47:56 +0000	[thread overview]
Message-ID: <aWhxfLwUvHDswsIY@casper.infradead.org> (raw)
In-Reply-To: <20260115031809.w7ksrj2ostwyxa54@inspiron>

On Thu, Jan 15, 2026 at 08:48:09AM +0530, Prithvi wrote:
> On Fri, Jan 09, 2026 at 12:07:00AM +0530, Prithvi wrote:
> > IIUC that would be the case when ocfs2_dio_end_io_write() operates on normal
> > files. However, according to the report of the bug, ocfs2_dio_end_io_write()
> > is holding &ocfs2_quota_ip_alloc_sem_key so I think due to random fuzzing by 
> > syzkaller, the function is curently operating on a quota file.

So the right fix is probably to disallow DIO to a quota file, wouldn't
you say?

  reply	other threads:[~2026-01-15  4:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 12:51 [PATCH] ocfs2: Fix circular locking dependency in ocfs2_del_inode_from_orphan() Prithvi Tambewagh
2026-01-08  1:29 ` Joseph Qi
2026-01-08 18:36   ` Prithvi
2026-01-15  3:18     ` Prithvi
2026-01-15  4:47       ` Matthew Wilcox [this message]
2026-01-17 17:42         ` Prithvi
2026-02-16  4:16         ` Prithvi
2026-02-23  5:05           ` Prithvi
2026-02-24  8:54             ` Heming Zhao
2026-02-28  5:12               ` Prithvi

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=aWhxfLwUvHDswsIY@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=activprithvi@gmail.com \
    --cc=david.hunter.linux@gmail.com \
    --cc=heming.zhao@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=khalid@kernel.org \
    --cc=linux-kernel-mentees@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    /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