Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 14 submissions in the queue.
posted by martyb on Monday July 13 2020, @08:41PM   Printer-friendly

Linus Torvalds' Initial Comment On Rust Code Prospects Within The Linux Kernel

Kernel developers appear to be eager to debate the merits of potentially allowing Rust code within the Linux kernel. Linus Torvalds himself has made some initial remarks on the topic ahead of the Linux Plumbers 2020 conference where the matter will be discussed at length.

[...] Linus Torvalds chimed in though with his own opinion on the matter. Linus commented that he would like it to be effectively enabled by default to ensure there is widespread testing and not any isolated usage where developers then may do "crazy" things. He isn't calling for Rust to be a requirement for the kernel but rather if the Rust compiler is detected on the system, Kconfig would enable the Rust support and go ahead in building any hypothetical Rust kernel code in order to see it's properly built at least.

Linus Torvalds Wishes Intel's AVX-512 A Painful Death

According to a mailing list post spotted by Phoronix, Linux creator Linus Torvalds has shared his strong views on the AVX-512 instruction set. The discussion arose as a result of recent news that Intel's upcoming Alder Lake processors reportedly lack support for AVX-512.

Torvalds' advice to Intel is to focus on things that matter instead of wasting resources on new instruction sets, like AVX-512, that he feels aren't beneficial outside the HPC market.

Related: Rust 1.0 Finally Released!
Results of Rust Survey 2016
AVX-512: A "Hidden Gem"?
Linus Torvalds Rejects "Beyond Stupid" Intel Security Patch From Amazon Web Services

Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Insightful) by Runaway1956 on Monday July 13 2020, @10:15PM (4 children)

    by Runaway1956 (2926) Subscriber Badge on Monday July 13 2020, @10:15PM (#1020772) Journal

    I did a search for "rust". I started scrolling - and scrolling - and scrolling - It took about half a day to scroll all the way through the various librust* libraries. Alright, maybe I exaggerate - it was less than six hours.

    Anyway, I'm reminded that most open source vulnerabilities are introduced by way of libraries that no one seems to control. []

    ‘Never trust a man whose uncle was eaten by cannibals’
    Starting Score:    1  point
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by The Mighty Buzzard on Monday July 13 2020, @11:14PM

    Base security of native Rust libraries is quite high compared to C/C++ but many of the libraries are not native Rust libraries; they're wrappers around shared libs installed on the system. Also, they're constantly in flux and the maintainers love nothing better than to introduce breaking changes because a shiny, new thing came out and they just have to use it in their lib.

    My rights don't end where your fear begins.
  • (Score: -1, Spam) by gtwregegcwcfew on Monday July 13 2020, @11:59PM (2 children)

    by gtwregegcwcfew (11552) on Monday July 13 2020, @11:59PM (#1020842)
    Useful piece of information! CeliTech []