public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>,
	Ritesh Harjani <ritesh.list@gmail.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Baokun Li <libaokun1@huawei.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2 2/2] ext4: protect ext4_release_dquot against freezing
Date: Thu, 6 Mar 2025 10:59:16 -0500	[thread overview]
Message-ID: <20250306155916.GA279274@mit.edu> (raw)
In-Reply-To: <Z8lBGaJGnM3SZZ-g@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>

On Thu, Mar 06, 2025 at 12:00:49PM +0530, Ojaswin Mujoo wrote:
> On Thu, Nov 21, 2024 at 06:08:55PM +0530, Ojaswin Mujoo wrote:
> > Protect ext4_release_dquot against freezing so that we
> > don't try to start a transaction when FS is frozen, leading
> > to warnings.
> > 
> > Further, avoid taking the freeze protection if a transaction
> > is already running so that we don't need end up in a deadlock
> > as described in
> > 
> >   46e294efc355 ext4: fix deadlock with fs freezing and EA inodes
> > 
> > Suggested-by: Jan Kara <jack@suse.cz>
> > Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
> 
> Hey Ted,
> 
> Just a ping, I think you might have missed this patch. Let me know if
> anything else is needed from my side.

Yes, I did miss this patch; thanks for the reminder. It looks good
and I've added it to my tree.

				- Ted

  reply	other threads:[~2025-03-06 16:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 12:38 [PATCH v2 0/2] Fix generic/390 failure due to quota release after freeze Ojaswin Mujoo
2024-11-21 12:38 ` [PATCH v2 1/2] quota: flush quota_release_work upon quota writeback Ojaswin Mujoo
2024-11-26  8:47   ` Jan Kara
2024-11-26 14:28   ` Baokun Li
2024-11-29  8:00   ` Disha Goel
2024-11-21 12:38 ` [PATCH v2 2/2] ext4: protect ext4_release_dquot against freezing Ojaswin Mujoo
2024-11-22  5:25   ` kernel test robot
2024-11-22  6:07   ` kernel test robot
2024-11-26  9:04   ` Jan Kara
2024-11-26 12:41     ` Ojaswin Mujoo
2024-11-26 14:49   ` Baokun Li
2024-11-27  6:01     ` Ojaswin Mujoo
2024-12-03  8:29       ` Baokun Li
2024-12-16  9:11         ` Ojaswin Mujoo
2024-11-28  4:58   ` Ritesh Harjani
2024-11-28 12:01     ` Jan Kara
2025-03-06  6:30   ` Ojaswin Mujoo
2025-03-06 15:59     ` Theodore Ts'o [this message]
2024-11-21 12:48 ` [PATCH v2 0/2] Fix generic/390 failure due to quota release after freeze Ojaswin Mujoo

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=20250306155916.GA279274@mit.edu \
    --to=tytso@mit.edu \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=libaokun1@huawei.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.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