Re: [PATCH -ndctl] cxl/memdev: Introduce sanitize-memdev functionality

[Alison Schofield <alison.schofield@intel.com>]

On Mon, Sep 30, 2024 at 02:39:33PM -0700, Davidlohr Bueso wrote:
> On Mon, 30 Sep 2024, Davidlohr Bueso wrote:\n

Hi David,

Checking on patches we noted as needing review in last months collab,
and now I'm thinking this one is pending a v2 from you. Is that right?

--Alison

> 
> >     cxl sanitize-memdev -e mem0 <-- secure erase
> >     cxl sanitize-memdev mem0 <-- sanitize
> 
> Not related to this patch (I will post v2), but just for future reference, and
> perhaps someone has thoughts. Whenever the kernel supports Media Operation
> (4402h in 3.1), I see this utility expanding to something like:
> 
>       cxl sanitize-memdev --zero A1-A2 [B1-B2 C1-C2] <-- zero-out ranges
>       cxl sanitize-memdev --zero mem0 <-- internally use all the mem0 range
>       cxl sanitize-memdev A1-A2 [B1-B2 C1-C2] <-- sanitize ranges
>       cxl sanitize-memdev -e A1-A2 [B1-B2 C1-C2] <-- error
> 
> ... and perhaps the kernel would need a security/zero as well as a
> security/{sanitize_range,zero_range} set of files.
> 
> Of course the underlying memdev for the specified ranges would still need to be
> offline entirely, just as is now.