linux-kernel - Re: [PATCH 0/3] fs: start to split up fs.h

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: <20251105-noten-bewiesen-3862ad2d7aea@brauner>
Date: Wed, 5 Nov 2025 14:48:06 +0100
From: Christian Brauner <brauner@...nel.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: linux-fsdevel@...r.kernel.org, 
	Alexander Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] fs: start to split up fs.h

On Wed, Nov 05, 2025 at 02:13:32PM +0100, Christian Brauner wrote:
> On Wed, Nov 05, 2025 at 04:55:34AM -0800, Christoph Hellwig wrote:
> > On Tue, Nov 04, 2025 at 03:46:31PM +0100, Christian Brauner wrote:
> > > Take first steps to split up fs.h. Add fs_super_types.h and fs_super.h
> > > headers that contain the types and functions associated with super
> > > blocks respectively.
> > 
> > We have this nice concept called directories for namespace prefixes.
> > Why not include/linux/fs/*.h for all these split out bits?
> 
> Sure, fine by me. Some do it differently. For example, mm has mm_* too.
> But yeah, the fs/ layout is fine.

/me raises eye-brows:

blk-cgroup.h          blkdev.h              blk-mq.h              blktrace_api.h
blk-crypto.h          blk-integrity.h       blkpg.h               blk_types.h
blk-crypto-profile.h  blk-mq-dma.h          blk-pm.h

What sort of mix-and-match bonanza have you got going on over there?