lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 24 Aug 2020 00:02:46 +0300
From:   Adrian Bunk <>
To:     Josh Triplett <>
Cc:     Nick Desaulniers <>,,,,
        Masahiro Yamada <>,
        Linus Torvalds <>,
        Greg KH <>,
        Miguel Ojeda <>,
        Steven Rostedt <>,
        LKML <>,
        clang-built-linux <>
Subject: Re: Linux kernel in-tree Rust support

On Sun, Jul 12, 2020 at 12:39:44PM -0700, Josh Triplett wrote:
> Rust has hard stability guarantees when upgrading from one stable
> version to the next. If code compiles with a given stable version of
> Rust, it'll compile with a newer stable version of Rust.

In librsvg, breakages with more recent Rust versions in the past year
required updates of two vendored crates:

For updating Rust in Debian stable for the next Firefox ESR update it 
would actually be useful if these violations of the "hard stability 
guarantee" in Rust get fixed, so that the old librsvg 2.44.10 builds 
again with the latest Rust.

It also makes me wonder how such regressions slip into Rust releases.


Powered by blists - more mailing lists