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: <CAOm6qnkoKjrUXCbhCiSYviuwCRVES1FYCy17fwATtyZ+M=Aw7g@mail.gmail.com>
Date: Thu, 9 Jan 2025 16:28:06 +0800
From: Weikang Guo <guoweikang.kernel@...il.com>
To: Alexander Gordeev <agordeev@...ux.ibm.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-s390@...r.kernel.org, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] arch/s390: save_area_alloc default failure behavior
 changed to panic

Hi, Alexander

>
> Alexander Gordeev <agordeev@...ux.ibm.com> wrote on Thursday, 9 January 2025 16:08
>
> On Thu, Jan 09, 2025 at 11:31:36AM +0800, Guo Weikang wrote:
>
> Hi Guo,
>
> > Now with the memblock_alloc_or_panic interface, save_area_alloc no longer
> > needs to handle panic itself.
> >
> > Signed-off-by: Guo Weikang <guoweikang.kernel@...il.com>
> > ---
> >  arch/s390/kernel/crash_dump.c | 4 +---
> >  arch/s390/kernel/numa.c       | 3 +--
> >  arch/s390/kernel/smp.c        | 4 ----
> >  3 files changed, 2 insertions(+), 9 deletions(-)
>
> This patch is a follow-up to v7, but instead it needs to be part of v8.
> I guess Andrew would refresh mm-everything (or whatever he finds appropriate)
> with the new version.

Sorry to confuse you, `memblock_alloc_or_panic`  is already merged
into mm/mm-everything
by Andrew, so this is an additional patch specifically to fix the
problem you mentioned.

This patch is based on the latest mm/mm-everything branch, and it  has
also been merged
by  Andrew，You should have received the email.

@Alexander  I hope I cleared your confusion.  ^ ^

>
> @Andrew, please correct me if I am wroing.
>
> Thanks!


Best regards.
---
Guo