linux-kernel - Re: [PATCH v2] Rust: kernel patch submission

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: <2025080925-varmint-food-b9a7@gregkh>
Date: Sat, 9 Aug 2025 08:59:11 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: AI talking about AI <aitalkingai@...il.com>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] Rust: kernel patch submission

On Fri, Aug 08, 2025 at 06:51:30PM -0300, AI talking about AI wrote:
> Hi all,
> 
> This is a two-patch series for the Rust-for-Linux tree:
> 
>   1) rust: mark CStr::to_str #[must_use] and update docs
>      - Adds an "# Errors" section explaining UTF-8 failure modes
>      - Prevents silent ignores by marking to_str() as #[must_use]
>      - Documents safety preconditions on as_str_unchecked()
> 
>   2) rust: clarify safety comments in workqueue.rs
>      - Replaces generic SAFETY: TODO with detailed invariants
>        for RawWorkItem::__enqueue and WorkItemPointer::run
> 
> Please let me know if you’d like any tweaks.
> 
> Thanks,
> —Slopisgood

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch was attached, please place it inline so that it can be
  applied directly from the email message itself.

- It looks like you did not use your "real" name for the patch on either
  the Signed-off-by: line, or the From: line (both of which have to
  match).  Please read the kernel file,
  Documentation/process/submitting-patches.rst for how to do this
  correctly.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot