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] [day] [month] [year] [list]

Message-ID: <f4f9c663-9ed5-40a0-858d-d7ac79cd3551@lucifer.local>
Date: Fri, 21 Feb 2025 17:40:59 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        Matthew Wilcox <willy@...radead.org>,
        David Hildenbrand <david@...hat.com>
Subject: Re: [PATCH v2] intel_th: avoid using deprecated page->mapping, index
 fields

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, we don't see it in linux-next yet, did you take this patch? Or just not
sync with -next?

As we'd like to assess the current state of pending 6.15 for page->index,
mapping usage to ensure we 'got' everything.

Thanks, Lorenzo

>
> Thanks,
> --
> Alex