linux-kernel - Re: [PATCH 00/13] [RFC] Rust support

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 29 Apr 2021 12:25:11 +0100
From:   Kajetan Puchalski <mrkajetanp@...il.com>
To:     mceier+kernel@...il.com
Cc:     ojeda@...nel.org, Linus Torvalds <torvalds@...ux-foundation.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        rust-for-linux@...r.kernel.org, linux-kbuild@...r.kernel.org,
        linux-doc@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/13] [RFC] Rust support


Mariusz Ceier <mceier+kernel@...il.com> writes:

> Rust compiler license doesn't require for people to give back to 
> the
> community - corporation can create their own version of rust 
> compiler
> adding some proprietary extensions, develop drivers with it and 
> even
> if the drivers code will be GPL'd they won't be buildable by 
> anyone
> but that corporation. The rust compiler license doesn't require
> sharing changes when you modify it. The similar problem has flex 
> and
> openssl required to build the kernel, but so far no one thought 
> about
> abusing them afaik.

Could you explain exactly what the issue you see there is?
Surely if someone develops a proprietary compiler and then writes 
kernel
drivers that use that compiler, nobody else will be able to build 
them.
Because of that, none of the maintainers will be able to run or 
test
the code and it'll never actually get merged into the kernel.
Surely they'd effectively be sabotaging themselves.

--
Kind regards,
Kajetan