From: Al Viro <viro@zeniv.linux.org.uk>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
ksummit@lists.linux.dev
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Rust
Date: Sun, 26 Jun 2022 04:18:58 +0100 [thread overview]
Message-ID: <YrfQItBxCWlvSfOq@ZenIV> (raw)
In-Reply-To: <YrfJ63hN+htFMQVA@mit.edu>
On Sat, Jun 25, 2022 at 10:52:27PM -0400, Theodore Ts'o wrote:
> ksmbd needs to interface with a large number of subsystems that are
> written in C. So even if you rewrite ksmbd in Rust, it will need to
> made a huge number of unsafe calls into C code.
Not to mention the fact that ksmbd bugs I've seen so far had nothing
to do with "memory safety" and they would translate into Rust just
fine, TYVM, even if the stuff outside of ksmbd had also been all in
Rust...
next prev parent reply other threads:[~2022-06-26 3:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 20:33 [TECH TOPIC] Rust Miguel Ojeda
2022-06-18 20:42 ` Laurent Pinchart
2022-06-18 20:42 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-18 20:44 ` Laurent Pinchart
2022-06-18 20:44 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-18 20:49 ` Miguel Ojeda
2022-06-19 6:13 ` Christoph Hellwig
2022-06-19 6:13 ` [Ksummit-discuss] " Christoph Hellwig
2022-06-19 10:04 ` Laurent Pinchart
2022-06-19 10:04 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 12:56 ` James Bottomley
2022-06-19 12:56 ` [Ksummit-discuss] " James Bottomley
2022-06-19 13:19 ` Jens Axboe
2022-06-19 13:19 ` [Ksummit-discuss] " Jens Axboe
2022-06-19 13:53 ` Laurent Pinchart
2022-06-19 13:53 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 14:27 ` James Bottomley
2022-06-19 14:27 ` [Ksummit-discuss] " James Bottomley
2022-06-19 14:45 ` [MAINTAINER SUMMIT] Are we becoming too fearful? [was Re: [TECH TOPIC] Rust] James Bottomley
2022-06-19 14:45 ` [Ksummit-discuss] " James Bottomley
2022-06-22 9:59 ` Linus Walleij
2022-06-22 10:57 ` Laurent Pinchart
2022-06-22 12:01 ` Linus Walleij
2022-06-22 12:09 ` Laurent Pinchart
2022-06-22 23:13 ` NeilBrown
2022-06-23 11:37 ` James Bottomley
2022-06-25 12:03 ` [Ksummit-discuss] " Mauro Carvalho Chehab
2022-06-25 11:45 ` [Ksummit-discuss] [TECH TOPIC] Rust Mauro Carvalho Chehab
2022-06-25 14:15 ` James Bottomley
2022-06-25 16:18 ` Mauro Carvalho Chehab
2022-06-25 22:29 ` Linus Walleij
2022-06-26 2:52 ` Theodore Ts'o
2022-06-26 3:18 ` Al Viro [this message]
2022-06-19 13:49 ` Laurent Pinchart
2022-06-19 13:49 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 19:08 ` Geert Uytterhoeven
2022-06-19 19:08 ` [Ksummit-discuss] " Geert Uytterhoeven
2022-06-19 20:57 ` Matthew Wilcox
2022-06-20 13:53 ` Linus Walleij
2022-06-20 14:08 ` James Bottomley
2022-06-21 15:11 ` Dan Carpenter
2022-06-23 10:58 ` [TECH TOPIC] Why is devm_kzalloc() harmful and what can we do about it Laurent Pinchart
2022-06-23 11:24 ` Dan Carpenter
2022-06-23 11:31 ` Laurent Pinchart
2022-06-21 9:49 ` [TECH TOPIC] Rust David Woodhouse
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=YrfQItBxCWlvSfOq@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=James.Bottomley@hansenpartnership.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=ksummit@lists.linux.dev \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=mchehab@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=tytso@mit.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).