linux-kernel - Re: [PATCH v5] f2fs: introduce device aliasing file

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZwyyiG0pqXoBFIW5@infradead.org>
Date: Sun, 13 Oct 2024 22:56:24 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Daeho Jeong <daeho43@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net,
	kernel-team@...roid.com, Daeho Jeong <daehojeong@...gle.com>,
	Chao Yu <chao@...nel.org>
Subject: Re: [PATCH v5] f2fs: introduce device aliasing file

On Thu, Oct 10, 2024 at 12:26:26PM -0700, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@...gle.com>
> 
> F2FS should understand how the device aliasing file works and support
> deleting the file after use. A device aliasing file can be created by
> mkfs.f2fs tool and it can map the whole device with an extrent, not

s/extrent/extent/g

> using node blocks. The file space should be pinned and normally used for
> read-only usages.

Is there an explanation somewhere what a 'device aliasing file' is?