From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [RFC][PATCHES] sock_alloc_file() cleanups and fixes Date: Mon, 4 Dec 2017 16:41:01 +0000 Message-ID: <20171204164100.GS21978@ZenIV.linux.org.uk> References: <20171201002027.GI21978@ZenIV.linux.org.uk> <20171204.103524.186631681746357000.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org To: David Miller Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:60680 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752990AbdLDQlG (ORCPT ); Mon, 4 Dec 2017 11:41:06 -0500 Content-Disposition: inline In-Reply-To: <20171204.103524.186631681746357000.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, Dec 04, 2017 at 10:35:24AM -0500, David Miller wrote: > From: Al Viro > Date: Fri, 1 Dec 2017 00:20:27 +0000 > > > 1) massage sys_socketpair() (should be a pure cleanup) > > 2) fix and clean up kcm_clone() (-stable fodder) > > 3) switch sock_alloc_file() to new calling conventions. > > > > It got some local testing, but it certainly needs more review. > > Diffstat for the entire thing is > > Series looks great to me: > > Acked-by: David S. Miller How do you prefer it to be handled? KCM one should go into everything since 4.6 (with trivial modifications in 4.11 and 4.12 - both had massaged the place around the call of kcm_clone() a bit, but this fix overwrites the entire area and that can be dropped into earlier kernels without any problems). I've put that into vfs.git#net-fixes and have the other two in vfs.git#for-davem on top of that, with you merging the latter into net-next.git and the former - into net.git. Is that OK with you, or would you prefer some other way of handling that kind of stuff?