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] [day] [month] [year] [list]
Message-ID: <Z91nVYgDeK8RhrSj@smile.fi.intel.com>
Date: Fri, 21 Mar 2025 15:19:17 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Pasha Tatashin <pasha.tatashin@...een.com>
Cc: changyuanl@...gle.com, graf@...zon.com, rppt@...nel.org,
	rientjes@...gle.com, corbet@....net, rdunlap@...radead.org,
	ilpo.jarvinen@...ux.intel.com, kanie@...ux.alibaba.com,
	ojeda@...nel.org, aliceryhl@...gle.com, masahiroy@...nel.org,
	akpm@...ux-foundation.org, tj@...nel.org, yoann.congal@...le.fr,
	mmaurer@...gle.com, roman.gushchin@...ux.dev, chenridong@...wei.com,
	axboe@...nel.dk, mark.rutland@....com, jannh@...gle.com,
	vincent.guittot@...aro.org, hannes@...xchg.org,
	dan.j.williams@...el.com, david@...hat.com,
	joel.granados@...nel.org, rostedt@...dmis.org,
	anna.schumaker@...cle.com, song@...nel.org, zhangguopeng@...inos.cn,
	linux@...ssschuh.net, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-mm@...ck.org,
	gregkh@...uxfoundation.org, tglx@...utronix.de, mingo@...hat.com,
	bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
	hpa@...or.com, rafael@...nel.org, dakr@...nel.org,
	bartosz.golaszewski@...aro.org, cw00.choi@...sung.com,
	myungjoo.ham@...sung.com, yesanishhere@...il.com,
	Jonathan.Cameron@...wei.com, quic_zijuhu@...cinc.com,
	aleksander.lobakin@...el.com, ira.weiny@...el.com, leon@...nel.org,
	lukas@...ner.de, bhelgaas@...gle.com, wagi@...nel.org,
	djeffery@...hat.com, stuart.w.hayes@...il.com, jgowans@...zon.com,
	jgg@...dia.com
Subject: Re: [RFC v1 1/3] luo: Live Update Orchestrator

On Thu, Mar 20, 2025 at 02:30:25PM -0400, Pasha Tatashin wrote:
> On Thu, Mar 20, 2025 at 1:50 PM Andy Shevchenko
> <andriy.shevchenko@...ux.intel.com> wrote:
> > On Thu, Mar 20, 2025 at 12:35:20PM -0400, Pasha Tatashin wrote:
> > > On Thu, Mar 20, 2025 at 9:40 AM Andy Shevchenko
> > > <andriy.shevchenko@...ux.intel.com> wrote:
> > > > On Thu, Mar 20, 2025 at 02:40:09AM +0000, Pasha Tatashin wrote:

...

> > > > > +EXPORT_SYMBOL_GPL(liveupdate_state_normal);
> > > >
> > > > No namespace?
> > >
> > > Namespace is 'liveupdate_', all public interfaces have this prefix,
> > > private functions are prefixed with luo_ where it makes sense.
> >
> > No, I'm talking about export namespace. Why does the entire kernel need these APIs?
> 
> These functions are intended for use by drivers and other subsystems
> participating in the live update.

Sure. Why can't they import API namespace when needed?
Btw, is this feature switchable? Then why would the rest of the kernel
need to see these APIs or load them?

> They allow these components to
> determine, during boot, whether to restore their state from the
> serialized state, or, during runtime, whether a live update is in the
> prepared state, causing different behavior compared to normal mode
> (e.g., prohibiting DMA mappings modifications, binding/unbinding,
> etc.).

-- 
With Best Regards,
Andy Shevchenko



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ