rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Xavier Denis <xldenis@lri.fr>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Taint Analysis for Kernel Rust
Date: Tue, 17 May 2022 13:03:50 +0200	[thread overview]
Message-ID: <CANiq72=kFrvrRqa+WGu_-jeda5xOA-Jq4RU5MUWuNzKb-vwr_A@mail.gmail.com> (raw)
In-Reply-To: <DA4D23F2-412B-4669-A079-A654735CE9B4@lri.fr>

On Tue, May 17, 2022 at 12:39 PM Xavier Denis <xldenis@lri.fr> wrote:
>
> Is there any interest in a prototype? Doesn’t the kernel already use a similar system for C?

Definitely, any analysis that is able to statically prove some
properties would be ideal, and any improvement over what the kernel
has now (whether for C or for Rust) would be welcome.

For debugging sleeps in atomic contexts, there is `might_sleep()` and
friends: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/kernel.h#n131

Another area that could be interesting to look at for feasibility of
new analyses is locking correctness, see lockdep:
https://www.kernel.org/doc/html/latest/locking/lockdep-design.html

> Right, I forgot about that, but if anything it slightly simplifies the work.

Indeed.

Cheers,
Miguel

      reply	other threads:[~2022-05-17 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 13:26 Taint Analysis for Kernel Rust Xavier Denis
2022-05-16 21:13 ` Miguel Ojeda
2022-05-17 10:39   ` Xavier Denis
2022-05-17 11:03     ` Miguel Ojeda [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANiq72=kFrvrRqa+WGu_-jeda5xOA-Jq4RU5MUWuNzKb-vwr_A@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=xldenis@lri.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).