From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH v2 1/2] sctp: add new getsockopt option SCTP_SOCKOPT_PEELOFF_KERNEL Date: Wed, 15 Jul 2015 13:58:24 -0700 (PDT) Message-ID: <20150715.135824.754282841801954470.davem@davemloft.net> References: <6091a8542d13f43fbe1abfa25062d28d15b15e66.1436891629.git.marcelo.leitner@gmail.com> <20150715131827.GA24091@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: marcelo.leitner@gmail.com, netdev@vger.kernel.org, vyasevich@gmail.com, linux-sctp@vger.kernel.org To: nhorman@tuxdriver.com Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:32774 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753500AbbGOU61 (ORCPT ); Wed, 15 Jul 2015 16:58:27 -0400 In-Reply-To: <20150715131827.GA24091@hmsreliant.think-freely.org> Sender: netdev-owner@vger.kernel.org List-ID: From: Neil Horman Date: Wed, 15 Jul 2015 09:18:28 -0400 > Do we need to do something here to prevent user space calls from inadvertently > accessing this option? And this is also not what I had anticipated was the implementation. I didn't mean that adding a new option number specially for the kernel was the right thing to do. I meant that having a specific function GPL exported to modules that the external code calls would do the trick. That's why we have things like kernel_sendmsg() et al.