linux-kernel - Re: [PATCH v3 5/5] dax: add PROBE_PREFER_ASYNCHRONOUS to the dax device driver

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: <CAAi7L5foTbvvskLxKW50T49bdUBbedoxQHifZ-4NJYf+Fv7YvA@mail.gmail.com>
Date: Thu, 20 Nov 2025 18:11:29 +0100
From: Michał Cłapiński <mclapinski@...gle.com>
To: Ira Weiny <ira.weiny@...el.com>
Cc: Dan Williams <dan.j.williams@...el.com>, Vishal Verma <vishal.l.verma@...el.com>, 
	Dave Jiang <dave.jiang@...el.com>, nvdimm@...ts.linux.dev, linux-cxl@...r.kernel.org, 
	Pasha Tatashin <pasha.tatashin@...een.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 5/5] dax: add PROBE_PREFER_ASYNCHRONOUS to the dax
 device driver

On Tue, Nov 18, 2025 at 10:46 PM Ira Weiny <ira.weiny@...el.com> wrote:
>
> Michal Clapinski wrote:
> > Signed-off-by: Michal Clapinski <mclapinski@...gle.com>
> > Reviewed-by: Dan Williams <dan.j.williams@...el.com>
>
> Sorry for the delay.  I picked up this series but I find that this breaks
> the device-dax and daxctl-create.sh.
>
> I was able to fix device-dax with a sleep, see below.
>
> I'm not 100% sure what to do about this.
>
> I don't want to sprinkle sleeps around the tests.  daxctl-create.sh also
> randomly fail due to the races introduced.  So not sure exactly where to
> sprinkle them without more work.

I see 2 possible solutions here:
1. Modify the tests to just poll for the devices to appear.
2. Modify ndctl to poll for the devices to appear before returning.

What do you think about those?

> Could dropping just this patch and landing the others achieve most of what
> you need?

No, device-dax is the only one I actually care about.