linux-kernel - Re: [RFC 3/4] block: set mapping order for the block cache in set_init

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: <e9604e71-bfd4-bf72-cb0b-b3dbcc492c3f@samsung.com>
Date:   Wed, 21 Jun 2023 14:02:57 +0200
From:   Pankaj Raghav <p.raghav@...sung.com>
To:     Hannes Reinecke <hare@...e.de>, <willy@...radead.org>,
        <david@...morbit.com>
CC:     <gost.dev@...sung.com>, <mcgrof@...nel.org>, <hch@....de>,
        <jwong@...nel.org>, <linux-fsdevel@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 3/4] block: set mapping order for the block cache in
 set_init_blocksize


>>
>> Hmm, which aops are you using for the block device? If you are using the old aops, then we will be
>> using helpers from buffer.c and mpage.c which do not support large folios. I am getting a BUG_ON
>> when I don't use iomap based aops for the block device:
>>
> I know. I haven't said that mpage.c / buffer.c support large folios _now_. All I'm saying is that I
> have a patchset enabling it to support large folios :-)
> 

Ah ok! I thought we are not going that route based on the discussion we had in LSF.

> Cheers,
> 
> Hannes
>