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: <CAJZ5v0j5+iB97rTqtOoFB0zpHzNOOHGOQVz51ZU--=4AcUPf-Q@mail.gmail.com>
Date: Mon, 9 Jun 2025 20:58:26 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Dave Jiang <dave.jiang@...el.com>, gregkh@...uxfoundation.org
Cc: Dan Williams <dan.j.williams@...el.com>, rafael.j.wysocki@...el.com, 
	linux-cxl@...r.kernel.org, linux-acpi@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Ben Cheatham <Benjamin.Cheatham@....com>, 
	Danilo Krummrich <dakr@...nel.org>, Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH 0/3] CXL: ACPI: faux: Fix cxl_core.ko module load regression

On Mon, Jun 9, 2025 at 5:04 PM Dave Jiang <dave.jiang@...el.com> wrote:
>
>
>
> On 6/6/25 8:32 PM, Dan Williams wrote:
> > git bisect flags:
> >
> > 6cb9441bfe8d ("ACPI: APEI: EINJ: Transition to the faux device interface")
> >
> > ...as the reason basic CXL unit tests are failing on latest mainline. In
> > addition to the fix to einj-core.c, this also needs some updates to
> > faux_device to make it behave more like platform_driver_probe(). Details
> > in the individual patches.
> >
> > Dan Williams (3):
> >   driver core: faux: Suppress bind attributes
> >   driver core: faux: Quiet probe failures
> >   ACPI: APEI: EINJ: Do not fail einj_init() on faux_device_create()
> >     failure
>
> LGTM
> Reviewed-by: Dave Jiang <dave.jiang@...el.com>
>
> >
> >  drivers/acpi/apei/einj-core.c | 9 +++------
> >  drivers/base/faux.c           | 3 ++-
> >  2 files changed, 5 insertions(+), 7 deletions(-)

Greg, I think it's better if I route this through the ACPI tree as the
issue being fixed was introduced through it.

Any concerns regarding this?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ