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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175152762861.887599.12834824712927485671.b4-ty@kernel.org>
Date: Thu, 03 Jul 2025 09:27:08 +0200
From: Carlos Maiolino <cem@...nel.org>
To: Youling Tang <youling.tang@...ux.dev>
Cc: linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Youling Tang <tangyouling@...inos.cn>, 
 Carlos Maiolino <cmaiolino@...hat.com>
Subject: Re: [PATCH v2] xfs: add FALLOC_FL_ALLOCATE_RANGE to supported
 flags mask

On Mon, 30 Jun 2025 09:11:48 +0800, Youling Tang wrote:
> Add FALLOC_FL_ALLOCATE_RANGE to the set of supported fallocate flags in
> XFS_FALLOC_FL_SUPPORTED. This change improves code clarity and maintains
> by explicitly showing this flag in the supported flags mask.
> 
> Note that since FALLOC_FL_ALLOCATE_RANGE is defined as 0x00, this addition
> has no functional modifications.
> 
> [...]

Applied to for-next, thanks!

[1/1] xfs: add FALLOC_FL_ALLOCATE_RANGE to supported flags mask
      commit: 9e9b46672b1daac814b384286c21fb8332a87392

Best regards,
-- 
Carlos Maiolino <cem@...nel.org>


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ