linux-kernel - Re: [linus:master] [mseal] 8be7258aad: stress-ng.pagemove.page_remaps_per

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: <87v80c8qoa.fsf@mail.lhotse>
Date: Wed, 07 Aug 2024 22:26:29 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Jeff Xu <jeffxu@...gle.com>, Nicholas Piggin <npiggin@...il.com>,
 Christophe Leroy <christophe.leroy@...roup.eu>, Pedro Falcato
 <pedro.falcato@...il.com>, kernel test robot <oliver.sang@...el.com>, Jeff
 Xu <jeffxu@...omium.org>, oe-lkp@...ts.linux.dev, lkp@...el.com,
 linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
 Kees Cook <keescook@...omium.org>, "Liam R. Howlett"
 <Liam.Howlett@...cle.com>, Dave Hansen <dave.hansen@...el.com>, Greg
 Kroah-Hartman <gregkh@...uxfoundation.org>, Guenter Roeck
 <groeck@...omium.org>, Jann Horn <jannh@...gle.com>, Jonathan Corbet
 <corbet@....net>, Jorge Lucangeli Obes <jorgelo@...omium.org>, Matthew
 Wilcox <willy@...radead.org>, Muhammad Usama Anjum
 <usama.anjum@...labora.com>, Stephen Röttger
 <sroettger@...gle.com>, Suren
 Baghdasaryan <surenb@...gle.com>, Amer Al Shanawany
 <amer.shanawany@...il.com>, Javier Carrasco
 <javier.carrasco.cruz@...il.com>, Shuah Khan <shuah@...nel.org>,
 linux-api@...r.kernel.org, linux-mm@...ck.org, ying.huang@...el.com,
 feng.tang@...el.com, fengwei.yin@...el.com
Subject: Re: [linus:master] [mseal] 8be7258aad:
 stress-ng.pagemove.page_remaps_per_sec -4.4% regression

Linus Torvalds <torvalds@...ux-foundation.org> writes:
> On Tue, 6 Aug 2024 at 05:03, Michael Ellerman <mpe@...erman.id.au> wrote:
>>
>> Or should I turn it into a series and post it?
>
> I think post it as a single working patch rather than as a series that
> breaks things and then fixes it.

It splits nicely with no breakage along the way.

> And considering that you did all the testing and found the problems,
> just take ownership of it and make it a "Suggested-by: Linus" or
> something.

Sure.

cheers