[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=aK-JJhpnZdeeGBtADrnXhyEp1Whw5+5rK6a4u85PhxA@mail.gmail.com>
Date: Tue, 4 May 2021 23:32:42 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Adrian Bunk <bunk@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Tom Stellard <tstellar@...hat.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
Fangrui Song <maskray@...gle.com>,
Serge Guelton <sguelton@...hat.com>,
Sylvestre Ledru <sylvestre@...illa.com>
Subject: Re: Very slow clang kernel config ..
On Sun, May 2, 2021 at 11:31 AM Adrian Bunk <bunk@...nel.org> wrote:
>
> Some of the new language ecosystems like Go or Rust do not offer
> shared libraries.
This is a bit misleading. Rust offers shared libraries, including the
option to offer a C ABI.
The problem are generics which, like C++ templates, cannot be swapped
at runtime. Distributions have had to deal with the STL, Boost, etc.
all these years too.
In fact, Rust improves things a bit: there are no headers that need to
be parsed from scratch every time.
> What happens if you use a program provided by your distribution that is
> written in Rust and handles untrusted input in a way that it might be
> vulnerable to exploits based on one of these CVEs?
>
> The program has a known vulnerability that will likely stay unfixed.
Why? I fail to see what is the issue rebuilding (or relinking) all
packages except distributions lacking enough compute resources.
Cheers,
Miguel
Powered by blists - more mailing lists