cxl_mem_sanitize(9)
bestie, welcome to the cxl_mem_sanitize(9) page from the Kernel API Manual β¨ this one is short but iconic, no cap.
π NAME π
cxl_mem_sanitize β Send a sanitization command to the device. π
β¨ SYNOPSIS β¨
int cxl_mem_sanitize (struct cxl_memdev *cxlmd , u16 cmd );
π«Ά ARGUMENTS π«Ά
cxlmdβ The device for the operation. π₯οΈcmdβ The specific sanitization command opcode. iykyk, it's the exact opcode. π
π₯ RETURN π₯
0 if the command was executed successfully, regardless of whether or not the actual security operation is done in the background, such as for the Sanitize case. So bestie, success here does not automatically mean the security thing is fully done β it can be doing its little background era. πβ¨
Error return values can be the result of the mailbox command, -EINVAL when security requirements are not met or invalid contexts, or -EBUSY if the sanitize operation is already in flight. π¨
π¦ DESCRIPTION π¦
See CXL 3.0 8.2.9.8.5.1 Sanitize and 8.2.9.8.5.2 Secure Erase. that's the lore, that's the vibe. ππ
π SEE ALSO π
- Kernel file
./drivers/cxl/core/mbox.ccxlmbox(9), cxl_internal_send_cmd(9)cxl_payload_from_user_allowed(9)cxl_validate_cmd_from_user(9)handle_mailbox_cmd_from_user(9)cxl_walk_cel(9)cxl_enumerate_cmds(9)cxl_mem_get_event_records(9)cxl_mem_get_partition_info(9)cxl_dev_state_identify(9)
okay that's the whole page, mwah π signing off with the footer energy: ./drivers/cxl/core β’ October 2026 β’ cxl_mem_sanitize(9) π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms