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: <20250625123903.GB28249@mit.edu>
Date: Wed, 25 Jun 2025 08:39:03 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Baokun Li <libaokun1@...wei.com>
Cc: "Pankaj Raghav (Samsung)" <kernel@...kajraghav.com>,
        Jan Kara <jack@...e.cz>, Luis Chamberlain <mcgrof@...nel.org>,
        Pankaj Raghav <p.raghav@...sung.com>, linux-ext4@...r.kernel.org,
        Zhang Yi <yi.zhang@...weicloud.com>
Subject: Re: LBS support for EXT4

On Wed, Jun 25, 2025 at 07:51:56PM +0800, Baokun Li wrote:
> Now that mainline ext4 supports buffer head large folios, we'll first
> focus on LBS support based on buffer heads. The main work involves adapting
> ext4's internal logic (e.g., block allocation, read/write operations,
> defragmentation) and clean up the process related to buffer head.

That makes sense; ext4 uses buffer heads for metadata blocks, and so
even if we were using the buffered iomap code, that only is relevant
to the data path, so the changes so that jbd2 and ext4 can suport
large blocks while updating inode table blocks, allocation bitmaps,
etc. would be needed anyway.

Cheers,

						- Ted

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ