linux-kernel - Re: [PATCH] arch/s390: save_area_alloc default failure behavior changed to panic

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: <20250109164315.b21f40e1b757b1cf9eb7e042@linux-foundation.org>
Date: Thu, 9 Jan 2025 16:43:15 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Weikang Guo <guoweikang.kernel@...il.com>
Cc: Alexander Gordeev <agordeev@...ux.ibm.com>, linux-s390@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org, Mike Rapoport
 <rppt@...ux.ibm.com>
Subject: Re: [PATCH] arch/s390: save_area_alloc default failure behavior
 changed to panic

On Thu, 9 Jan 2025 22:53:57 +0800 Weikang Guo <guoweikang.kernel@...il.com> wrote:

> I understand your point, you want to modify directly based on the
> original patch.
> If we repost it,it may not  be v8  but  v9.
> 
> Last v8 patch: https://lkml.kernel.org/r/20250102072528.650926-1-guoweikang.kernel@gmail.com
> 
> I reduced the recipients for V8 because I remembered that the number
> of CCs might
> have exceeded the limit at the time, and there hadn't been any
> comments on V7 for a long time
> 
> > @Andrew, is that still possible?
> 
> @Andrew, I can cooperate if necessary, I could merge them into one
> patch and repost.

I'll fold this patch ("arch/s390: save_area_alloc default failure
behavior changed to panic") into
"mm-memblock-add-memblock_alloc_or_panic-interface.patch", v8 before
sending the latter upstream.

But I'm not sure that we've completed the review discussion of
"mm/memblock: add memblock_alloc_or_panic interface" with Mike?