From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Wessel Subject: Re: [RFC] remove netpoll receive code Date: Wed, 17 Oct 2007 22:52:39 -0500 Message-ID: <4716D887.2020209@windriver.com> References: <20071017132131.1992bedd@freepuppy.rosehill> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "David S. Miller" , Andrew Morton , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Stephen Hemminger Return-path: Received: from mail.windriver.com ([147.11.1.11]:60609 "EHLO mail.wrs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754641AbXJRDxt (ORCPT ); Wed, 17 Oct 2007 23:53:49 -0400 In-Reply-To: <20071017132131.1992bedd@freepuppy.rosehill> Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Kgdb has been submitted for inclusion in the mainline kernel at this point, along with an additional change to the netpoll rx path. If it is the case that this needs to be implemented in another manner, that is ok but please do let me know what the plans are for the API so that the kgdboe code can be adapted. Thanks, Jason. Stephen Hemminger wrote: > The netpoll receive code is: > 1. Not used by any in-tree features, it is used by kgdb-over-ether. > 2. A nice hook for people doing nasty things like private binary network stacks or rootkits. > 3. Unsecured by any of the normal firewalling code. > > Hopefully all distro's are smart enough to turn it off in their default config *nudge, nudge*. > Doubly true for any distribution that claims to be secure or enterprise ready. > > I propose that we take out all the whole netpoll rx path. If/when kgdb gets submitted > a better and alternative receive path can be added. > >