linux-kernel - Re: [f2fs-dev] [PATCH v3 1/2] f2fs: avoid redundant clean nat entry move in lru list

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <175372142024.776676.5036079944268949062.git-patchwork-notify@kernel.org>
Date: Mon, 28 Jul 2025 16:50:20 +0000
From: patchwork-bot+f2fs@...nel.org
To: wangzijie <wangzijie1@...or.com>
Cc: jaegeuk@...nel.org, chao@...nel.org, linux-kernel@...r.kernel.org,
 feng.han@...or.com, linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: avoid redundant clean nat entry
 move in lru list

Hello:

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

On Mon, 28 Jul 2025 13:02:35 +0800 you wrote:
> __lookup_nat_cache follows LRU manner to move clean nat entry, when nat
> entries are going to be dirty, no need to move them to tail of lru list.
> Introduce a parameter 'for_dirty' to avoid it.
> 
> Signed-off-by: wangzijie <wangzijie1@...or.com>
> ---
> v3:
> - followed by Chao's suggestion to update comments
> v2:
> - followed by Jaegeuk's suggestion to add a parameter in __lookup_nat_cache
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v3,1/2] f2fs: avoid redundant clean nat entry move in lru list
    https://git.kernel.org/jaegeuk/f2fs/c/0349b7f95c80
  - [f2fs-dev,v3,2/2] f2fs: directly add newly allocated pre-dirty nat entry to dirty set list
    https://git.kernel.org/jaegeuk/f2fs/c/40aa9e1223fd

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