From: James Morris <jmorris@namei.org>
To: Christian Brauner <brauner@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>
Cc: Greg KH <greg@kroah.com>,
gmonaco@redhat.com, ojeda@kernel.org, aliceryhl@google.com,
gary@garyguo.net, namcao@linutronix.de, sashal@kernel.org,
natalie.klaus@runtimeverification.com, willy@infradead.org,
paulmck@kernel.org, corinnt@google.com,
stewart@linuxfoundation.org, linux-kernel@vger.kernel.org,
Paul Moore <paul@paul-moore.com>,
tytso@mit.edu, keisuke.nishimura@inria.fr,
jean-pierre.lozi@inria.fr
Subject: Kernel formal methods mailing list?
Date: Tue, 3 Nov 2026 15:59:52 -0800 (PST) [thread overview]
Message-ID: <ed89f1ce-cdca-d6f6-3e1-f0fa34eac4d@namei.org> (raw)
Hi Folks,
I've tried to include folk who are known to be working on formal
verification for the Linux kernel. Apologies if I've missed anyone and
please forward as appropriate.
Several Linux kernel developers & researchers have been experimenting
with formal methods in recent times, I think largely due to the potential
of LLMs to lower some of the costs and barriers to entry.
Examples I'm aware of include a presentation by Corinn Tiffany at LPC on
her work with XArray [1], and Christian Brauner's linux-formal repo [2].
I've been experimenting with formal verification as part of a hypervisor
research project [3] (which is admittedly not the kernel).
I'm interested in learning from what others are doing in this area, and
sharing potentially useful findings, especially in terms of identifying
_practical_ approaches for verification of low-level systems code.
I suspect there's a lot that can be done on smaller scale, well-defined
projects, by developers who don't necessarily have specific expertise in
formal methods, but have deep expertise in the target subsystem.
Thoughts? Would it be worth setting up a mailing list?
[1] https://lpc.events/event/20/contributions/2540/
[2] https://github.com/brauner/linux-formal
[3] https://github.com/orgs/beryllium-project/repositories (WIP review snapshot)
--
James Morris
<jmorris@namei.org>
next reply other threads:[~2026-11-03 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 23:59 James Morris [this message]
2026-11-04 2:57 ` Natalie Klaus
2026-11-04 11:22 ` Greg KH
2026-11-04 13:23 ` Miguel Ojeda
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=ed89f1ce-cdca-d6f6-3e1-f0fa34eac4d@namei.org \
--to=jmorris@namei.org \
--cc=aliceryhl@google.com \
--cc=brauner@kernel.org \
--cc=corinnt@google.com \
--cc=gary@garyguo.net \
--cc=gmonaco@redhat.com \
--cc=greg@kroah.com \
--cc=jean-pierre.lozi@inria.fr \
--cc=julia.lawall@inria.fr \
--cc=keisuke.nishimura@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=natalie.klaus@runtimeverification.com \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=paulmck@kernel.org \
--cc=sashal@kernel.org \
--cc=stewart@linuxfoundation.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®