linux-kernel - Re: [PATCH] block: Name the RQF flags enum

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: <174130870132.334915.1531694322372614000.b4-ty@kernel.dk>
Date: Thu, 06 Mar 2025 17:51:41 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Breno Leitao <leitao@...ian.org>
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, 
 bpf@...r.kernel.org, kernel-team@...a.com, 
 Yonghong Song <yonghong.song@...ux.dev>
Subject: Re: [PATCH] block: Name the RQF flags enum


On Thu, 06 Mar 2025 08:27:51 -0800, Breno Leitao wrote:
> Commit 5f89154e8e9e3445f9b59 ("block: Use enum to define RQF_x bit
> indexes") converted the RQF flags to an anonymous enum, which was
> a beneficial change. This patch goes one step further by naming the enum
> as "rqf_flags".
> 
> This naming enables exporting these flags to BPF clients, eliminating
> the need to duplicate these flags in BPF code. Instead, BPF clients can
> now access the same kernel-side values through CO:RE (Compile Once, Run
> Everywhere), as shown in this example:
> 
> [...]

Applied, thanks!

[1/1] block: Name the RQF flags enum
      commit: e7112524e5e885181cc5ae4d258f33b9dbe0b907

Best regards,
-- 
Jens Axboe