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] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZDzmtK64elHn6yPg@infradead.org>
Date:   Sun, 16 Apr 2023 23:27:00 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Hannes Reinecke <hare@...e.de>
Cc:     Christoph Hellwig <hch@...radead.org>,
        Pankaj Raghav <p.raghav@...sung.com>,
        Matthew Wilcox <willy@...radead.org>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        mcgrof@...nel.org
Subject: Re: [PATCH] mm/filemap: allocate folios according to the blocksize

On Mon, Apr 17, 2023 at 08:08:04AM +0200, Hannes Reinecke wrote:
> On 4/17/23 06:36, Christoph Hellwig wrote:
> > On Fri, Apr 14, 2023 at 03:49:08PM +0200, Hannes Reinecke wrote:
> > > If the blocksize is larger than the pagesize allocate folios
> > > with the correct order.
> > 
> > And how is that supposed to actually happen?
> 
> By using my patcheset to brd and set the logical blocksize to eg 16k.

Then add it to your patchset instead of trying to add dead code to the
kernel while also losing context.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ