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: <aE_a4_rGbMLJKBIs@localhost.localdomain>
Date: Mon, 16 Jun 2025 10:50:43 +0200
From: Oscar Salvador <osalvador@...e.de>
To: David Hildenbrand <david@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	Vlastimil Babka <vbabka@...e.cz>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Harry Yoo <harry.yoo@...cle.com>, Rakie Kim <rakie.kim@...com>,
	Hyeonggon Yoo <42.hyeyoo@...il.com>,
	Joshua Hahn <joshua.hahnjy@...il.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 03/10] mm,memory_hotplug: Implement numa node notifier

On Mon, Jun 16, 2025 at 10:39:24AM +0200, David Hildenbrand wrote:
> It's suboptimal yes, But to get it right, you'd have to remmeber for exactly
> which notofiers you performed the calls ...

Yeah, definitely not straightforward.

> > I mean, yes, I guess we can put the burden on the users of
> > the notifiers to not assume anything, but then yes, I think we should document this
> > as it can lead to potential misbeliefs.
> 
> The burden is already on the users I think.

Yes, it's already on them, although I'm not sure if all of them are aware
though.
But anyway, let's just document it to have the ruleset clear.


-- 
Oscar Salvador
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ