linux-kernel - Re: [PATCHSET v8 0/12] Uncached buffered IO

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: <y77zzxdd523ozv2awanakiemd7m2fb4ktpsmlp2evpohnllusw@gcmleh7vpjkr>
Date: Thu, 16 Jan 2025 12:06:45 +0200
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Jens Axboe <axboe@...nel.dk>, linux-mm@...ck.org, 
	linux-fsdevel@...r.kernel.org, hannes@...xchg.org, clm@...a.com, linux-kernel@...r.kernel.org, 
	willy@...radead.org, bfoster@...hat.com
Subject: Re: [PATCHSET v8 0/12] Uncached buffered IO

On Mon, Jan 13, 2025 at 04:46:50PM -0800, Andrew Morton wrote:
> > > Also, consuming a new page flag isn't a minor thing.  It would be nice
> > > to see some justification around this, and some decription of how many
> > > we have left.
> > 
> > For sure, though various discussions on this already occurred and Kirill
> > posted patches for unifying some of this already. It's not something I
> > wanted to tackle, as I think that should be left to people more familiar
> > with the page/folio flags and they (sometimes odd) interactions.
> 
> Matthew & Kirill: are you OK with merging this as-is and then
> revisiting the page-flag consumption at a later time?

I have tried to find a way to avoid adding a new flag bit, but I have not
found one. I am okay with merging it as it is.

-- 
  Kiryl Shutsemau / Kirill A. Shutemov