Richard Weinberger
Posts
3Following
HiddenFollowers
Hidden
Richard Weinberger
repeated
repeated
Lorenzo Stoakes
ljs
Judging from the absolutely packed out rust sessions I went to at LPC and the very positive support from senior people including especially @gregkh it is super clear to me that rust is here to stay in the kernel and a big part of its future.
Have offered to help (or at least be cc'd in hopes I have time for it :) on mm binding stuff fwiw from the kernel side.
And also I really do have to sit down with rust finally... Maybe advent of code this year...
Have offered to help (or at least be cc'd in hopes I have time for it :) on mm binding stuff fwiw from the kernel side.
And also I really do have to sit down with rust finally... Maybe advent of code this year...
3
27
61
Richard Weinberger
repeated
repeated
Richard Weinberger
repeated
repeated
Karmina the MycoWitch
kittycatdance@todon.eu
it's fine September ~ Vienna edition.
#climatecrisis #vienna #oida
3
7
3
Richard Weinberger
repeated
repeated
Greg K-H
gregkh
This "untrusted data" patch series from Benno Lossin is the result of conversations at last weekend's Rust Linux kernel conference in Copenhagen:
https://lore.kernel.org/all/20240913112643.542914-1-benno.lossin@proton.me/
It's not a "silver bullet" for why we should be using rust in the Linux kernel, but it is a "big giant sledgehammer" to help squash and prevent from happening MANY common types of kernel vulnerabilities and bugs (remember, "all input is evil!" and this change forces you to always be aware of that, which is something that C in the kernel does not.)
I had always felt that Rust was the future for what we need to do in Linux, but now I'm sure, because if we can do stuff like this, with no overhead involved (it's all checked at build time), then we would be foolish not to give it a real try.
And yes, I've asked for this for years from the C developers, and maybe we can also do it there, but it's not obvious how and no one has come up with a way to do so. Maybe now they will have some more incentive :)
https://lore.kernel.org/all/20240913112643.542914-1-benno.lossin@proton.me/
It's not a "silver bullet" for why we should be using rust in the Linux kernel, but it is a "big giant sledgehammer" to help squash and prevent from happening MANY common types of kernel vulnerabilities and bugs (remember, "all input is evil!" and this change forces you to always be aware of that, which is something that C in the kernel does not.)
I had always felt that Rust was the future for what we need to do in Linux, but now I'm sure, because if we can do stuff like this, with no overhead involved (it's all checked at build time), then we would be foolish not to give it a real try.
And yes, I've asked for this for years from the C developers, and maybe we can also do it there, but it's not obvious how and no one has come up with a way to do so. Maybe now they will have some more incentive :)
5
123
166
Richard Weinberger
repeated
repeated
Jonathan Corbet
corbet
I have often complained that, even though thousands of developers are paid to work on the Linux kernel, there is not a single person whose job it is to write documentation for the kernel. The problem is wider than that, though: Alejandro Colomar, who has been maintaining the man pages collection for the last four years, can no longer afford to do it for free.
https://lwn.net/ml/all/4d7tq6a7febsoru3wjium4ekttuw2ouocv6jstdkthnacmzr6x@f2zfbe5hs7h5
https://lwn.net/ml/all/4d7tq6a7febsoru3wjium4ekttuw2ouocv6jstdkthnacmzr6x@f2zfbe5hs7h5
5
84
66
Richard Weinberger
repeated
repeated
K. Ryabitsev
monsieuricon
Me, when I start explaining DMARC, DKIM and how they work with mailing lists.
3
6
33
Richard Weinberger
rw
I'll try to post here more often. Let's start with a brick stone tux I built this afternoon.
Moc credit: https://www.t-reichling.de/de/mocs_littletux.shtml
Moc credit: https://www.t-reichling.de/de/mocs_littletux.shtml
0
0
1