linux-kernel - Re: [PATCH 6.1.y 0/7] Backport patches for DAMON merge regions fix

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2024071624-mustiness-quarterly-f34e@gregkh>
Date: Tue, 16 Jul 2024 20:23:46 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: SeongJae Park <sj@...nel.org>
Cc: stable@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
	damon@...ts.linux.dev, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6.1.y 0/7] Backport patches for DAMON merge regions fix

On Tue, Jul 16, 2024 at 10:51:58AM -0700, SeongJae Park wrote:
> Commit 310d6c15e910 ("mm/damon/core: merge regions aggressively when
> max_nr_regions") causes a build warning [1] on 6.1.y.  That was due to
> unnecessarily strict type check from max().
> 
> Fix the warning by backporting a minmax.h upstream commit that made the
> type check less strict for unnecessary case, and upstream commits that
> it depends on.
> 
> Note that all patches except the third one ("minmax: fix header
> inclusions") are clean cherry-picks of upstream commit.  For the third
> one, a minor conflict fix was needed.
> 
> [1] https://lore.kernel.org/2024071519-janitor-robe-779f@gregkh

Thanks for these, I'll queue them up after this round of -rc releases go
out in a few days.

greg k-h