linux-kernel - linux-next: manual merge of the slab tree with the mm-unstable tree

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

Message-ID: <20250721142001.3d1c8777@canb.auug.org.au>
Date: Mon, 21 Jul 2025 14:20:01 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Vlastimil Babka <vbabka@...e.cz>, Andrew Morton
 <akpm@...ux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, Luiz Capitulino
 <luizcap@...hat.com>, "Matthew Wilcox (Oracle)" <willy@...radead.org>
Subject: linux-next: manual merge of the slab tree with the mm-unstable tree

Hi all,

Today's linux-next merge of the slab tree got a conflict in:

  fs/proc/page.c

between commit:

  a602ee331e31 ("fs: stable_page_flags(): use snapshot_page()")

from the mm-unstable tree and commit:

  d8178294c53e ("proc: Remove mention of PG_slab")

from the slab tree.

I fixed it up (I just used the former version) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging.  You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped