linux-kernel - Re: bio_vec, bv

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]

Date: Tue, 02 Jan 2024 10:03:58 +0000
From: David Howells <dhowells@...hat.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: dhowells@...hat.com, Christoph Hellwig <hch@....de>,
    linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
    linux-kernel@...r.kernel.org
Subject: Re: bio_vec, bv_page and folios

Matthew Wilcox <willy@...radead.org> wrote:

> On Tue, Jan 02, 2024 at 08:56:46AM +0000, David Howells wrote:
> > Hi Christoph, Willy,
> > 
> > Will bv_page in struct bio_vec ever become a folio pointer rather than I page
> > pointer?  I'm guessing not as it still presumably needs to be able to point to
> > non-folio pages.
> 
> My plan for bio_vec is that it becomes phyr -- a physical address +
> length.  No more page or folio reference.

Interesting...  What does that mean for those places that currently use
bv_page as a place to stash a pointer to the page and use it to clean up the
page later?

David