From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v2 net-next 0/2] kcm: fix two syzcaller issues Date: Wed, 24 Jan 2018 15:54:45 -0500 (EST) Message-ID: <20180124.155445.1219599573440727295.davem@davemloft.net> References: <20180124203541.3172-1-tom@quantonium.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, rohit@quantonium.net, jchapman@katalix.com, g.nault@alphalink.fr To: tom@quantonium.net Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:49898 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932114AbeAXUyr (ORCPT ); Wed, 24 Jan 2018 15:54:47 -0500 In-Reply-To: <20180124203541.3172-1-tom@quantonium.net> Sender: netdev-owner@vger.kernel.org List-ID: From: Tom Herbert Date: Wed, 24 Jan 2018 12:35:39 -0800 > In this patch set: > > - Don't allow attaching non-TCP or listener sockets to a KCM mux. > - In kcm_attach Check if sk_user_data is already set. This is > under lock to avoid race conditions. More work is need to make > all of the users of sk_user_data to use the same locking. > > - v2 > Remove unncessary check for not PF_KCM in kcm_attach (suggested by > Guillaume Nault) Series applied, thanks Tom.