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: <b12548c7-9f1c-48bc-a728-d169fcd5e16f@kuka.com>
Date: Wed, 14 May 2025 17:59:23 +0200
From: Ignacio Moreno Gonzalez <Ignacio.MorenoGonzalez@...a.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
 "Liam R. Howlett" <Liam.Howlett@...cle.com>, yang@...amperecomputing.com,
 willy@...radead.org, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: madvise: make MADV_NOHUGEPAGE a no-op if !THP

On 5/14/2025 5:27 PM, Lorenzo Stoakes wrote:

>> On 5/14/2025 3:52 PM, Lorenzo Stoakes wrote:
> 
> Igancio - you're deleting too much context here, you did it in the other email
> too, it's really hard to follow what's going on. Please try to be careful about
> what bits of an email you delete when quoting.
> 
> You're putting my comment here without the context of what I asked Andrew, so
> now it's not clear what's going on.
> 

Hi Lorenzo,

Sorry about that and thanks for letting me know. I appreciate your advice, since I am new in the mailing list. I will try to include more context to avoid confusion in the future :)


>>> I have pinged s390 people on there, but I don't think this is going to make this
>>> cycle given we will probably need to coordinate with them to fix up this enum
>>> name (which seems the best solution to me!...)
>>
>> They answered that it would be ok for them to do a quick fix over the mm tree:
>>
>> https://lore.kernel.org/linux-mm/6f8f3780-902b-49d4-a766-ea2e1a8f85ea@linux.ibm.com/
> 
> Yeah, we need to figure out who's going to do this patch though :)
> 
> Did you want to Iganacio?
> 
> I would suggest chasing up with them to see if they plan to do it or you ought
> to do so.
> 
> I can also do it if you need it quick, but I don't want to deprive you of the
> opportunity to patch that :)

For me it's fine if you create the patch. That will probably be faster ;)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ