From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3244772 for ; Tue, 20 Jul 2021 14:04:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=q6TFtqlNed5wHB8q1aBQTiurdHjRpb5zdPSpLrkpX8w=; b=Bu2jDT0vpTQdys+CAeIAHVZEDC 1Gc0YQ9+P+rjMIlQGvxQjIubghIJI3HSDV9TPkXoMejpcaDvXkw4PvQicj4msqVW4UFC2LGqg97UI ivGSqTHa4eRmQbAZ9o6WOkqu+4DpAbX+AeU0ye382QLYpbPpAikzMpPb2r4uyZc9gQoY=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1m5qMY-00E3r9-Vo; Tue, 20 Jul 2021 16:04:46 +0200 Date: Tue, 20 Jul 2021 16:04:46 +0200 From: Andrew Lunn To: Miguel Ojeda Cc: Wedson Almeida Filho , Linus Walleij , Greg KH , Bartosz Golaszewski , Kees Cook , Jan Kara , James Bottomley , Julia Lawall , Laurent Pinchart , Roland Dreier , ksummit@lists.linux.dev, Viresh Kumar Subject: Re: [TECH TOPIC] Rust for Linux Message-ID: References: Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Jul 20, 2021 at 03:38:24PM +0200, Miguel Ojeda wrote: > On Tue, Jul 20, 2021 at 3:21 PM Andrew Lunn wrote: > > > > Part of the issue here is -stable and back porting fixes. If files > > move around within the tree, it makes this back porting harder. git > > cherry-pick is a lot less likely to work, it needs more manual > > intervention. I expect it will make the stable teams job much easier > > if these files are in the right place from day 1 and never move. > > We can definitely move things already if we agree on a particular > approach -- we definitely do not want to make anybody's job harder. > > An alternative could be stating that Rust support will not get > backports for e.g. the first two or three releases to give it a bit of > time to mature in-tree; while making it easier to get maintainers > involved and in general everything rolling. Let see what the stable team say about that. But it is well known that it is hard to separate security fixes out from other bug fixes. So by not back porting, you are potentially leaving open security issues. I guess these will be in the unsafe code, and that seems to be mostly in the files we are talking about. Andrew