linux-kernel - Re: [PATCH v2] intel_th: avoid using deprecated page->mapping, index fields

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: <Z-qLN0R2frlq2QcR@casper.infradead.org>
Date: Mon, 31 Mar 2025 13:31:51 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	David Hildenbrand <david@...hat.com>
Subject: Re: [PATCH v2] intel_th: avoid using deprecated page->mapping, index
 fields

On Mon, Mar 31, 2025 at 09:36:40AM +0300, Alexander Shishkin wrote:
> Matthew Wilcox <willy@...radead.org> writes:
> 
> > On Wed, Jan 29, 2025 at 01:39:06PM +0200, Alexander Shishkin wrote:
> >> Lorenzo Stoakes <lorenzo.stoakes@...cle.com> writes:
> >> 
> >> > Thanks very much! Yeah just keen to get this in as we are moving towards
> >> > removing these fields very soon.
> >> 
> >> My understanding is that this is a part of larger effort to reduce
> >> struct page to 8 bytes and an optionally dynamically allocated slightly
> >> larger structure, is that correct? Just curious.
> >> 
> >> > Could you take this in your tree? I think that'd work best.
> >> 
> >> Sure, will do.
> >
> > Hi, this doesn't appear to be in linux-next yet.  Could you confirm it's
> > scheduled to hit the next merge window?
> 
> Yes, I'll send it to Greg once -rc1 is tagged.

What?!  This should be in *BEFORE RC1*!