BPF List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: MCB-SMART-BOY <mcb2720838051@gmail.com>
Cc: rust-for-linux@vger.kernel.org, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] Rust BPF Verifier Implementation
Date: Mon, 29 Dec 2025 07:59:46 +0100	[thread overview]
Message-ID: <2025122915-distort-concrete-2e5f@gregkh> (raw)
In-Reply-To: <20251228190455.176910-1-mcb2720838051@gmail.com>

On Sun, Dec 28, 2025 at 07:04:55PM +0000, MCB-SMART-BOY wrote:
> Hello Rust for Linux and BPF maintainers,
> 
> I would like to submit an RFC for a complete Rust implementation of the
> Linux kernel's BPF verifier (kernel/bpf/verifier.c) as part of the Rust
> for Linux project.

This was already discussed and rejected (i.e. do not rewrite existing
C code in rust unless you are the owner/maintainer of it).  Why bring
this up again?

thanks,

greg k-h

      reply	other threads:[~2025-12-29  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-28 19:04 [RFC PATCH 0/1] Rust BPF Verifier Implementation MCB-SMART-BOY
2025-12-29  6:59 ` Greg KH [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=2025122915-distort-concrete-2e5f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcb2720838051@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    /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