Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix potential deadlock due to unpaired
 node_write lock use
From:   patchwork-bot+f2fs@kernel.org
Message-Id: <168437462152.19511.17219175731809504338.git-patchwork-notify@kernel.org>
Date:   Thu, 18 May 2023 01:50:21 +0000
References: <20230514080723.17313-1-chao@kernel.org>
In-Reply-To: <20230514080723.17313-1-chao@kernel.org>
To:     Chao Yu <chao@kernel.org>
Cc:     jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
        linux-f2fs-devel@lists.sourceforge.net
Precedence: bulk

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Sun, 14 May 2023 16:07:23 +0800 you wrote:
> If S_NOQUOTA is cleared from inode during data page writeback of quota
> file, it may miss to unlock node_write lock, result in potential
> deadlock, fix to use the lock in paired.
> 
> Kworker					Thread
> - writepage
>  if (IS_NOQUOTA())
>    f2fs_down_read(&sbi->node_write);
> 					- vfs_cleanup_quota_inode
> 					 - inode->i_flags &= ~S_NOQUOTA;
>  if (IS_NOQUOTA())
>    f2fs_up_read(&sbi->node_write);
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix potential deadlock due to unpaired node_write lock use
    https://git.kernel.org/jaegeuk/f2fs/c/a731b6aefbb4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html