linux-kernel - Re: Rust kernel policy

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: <615ce44fa528ad7be28ba518e14a970f04481078.camel@kernel.org>
Date: Wed, 19 Feb 2025 08:20:31 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>, Miguel Ojeda	
 <miguel.ojeda.sandonis@...il.com>, rust-for-linux	
 <rust-for-linux@...r.kernel.org>, Linus Torvalds
 <torvalds@...ux-foundation.org>,  Greg KH <gregkh@...uxfoundation.org>,
 David Airlie <airlied@...il.com>, 	linux-kernel@...r.kernel.org,
 ksummit@...ts.linux.dev
Subject: Re: Rust kernel policy

On Tue, 2025-02-18 at 13:22 -0800, Boqun Feng wrote:
> FWIW, usually Rust code has doc tests allowing you to run it with
> kunit,
> see:
> 
> 	https://docs.kernel.org/rust/testing.html	

I know this document and this was what I used to compile DMA patches.
Then I ended up into "no test, no go" state :-)

I put this is way. If that is enough, or perhaps combined with
submitting-patches.rst, why this email thread exists?

> 
> , I took a look at the DMA patches, there is one doc test, but
> unfortunately it's only a function definition, i.e. it won't run
> these
> DMA bindings.
> 
> I agree that test payload should be provided, there must be something
> mentioning this in Documentation/process/submitting-patches.rst
> already?

Partly yes. This what was exactly what I was wondering when I read
through the thread, i.e. why no one is speaking about tests :-)

> 
> Regards,
> Boqun

Thanks for responding, definitely not picking a fight here. I
actually just wanted to help, and doing kernel QA is the best
possible way to take the first baby steps on a new subsystem,
and sort of area where I'm professional already as a kernel
maintainer.

BR, Jarkko