Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161530AbWJLJva (ORCPT ); Thu, 12 Oct 2006 05:51:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161531AbWJLJva (ORCPT ); Thu, 12 Oct 2006 05:51:30 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:51589 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1161530AbWJLJv3 (ORCPT ); Thu, 12 Oct 2006 05:51:29 -0400 Subject: Re: [patch 03/19] SUNRPC: avoid choosing an IPMI port for RPC traffic From: Alan Cox To: Matt Domsch Cc: Trond Myklebust , Jan Engelhardt , Greg KH , linux-kernel@vger.kernel.org, stable@kernel.org, Justin Forbes , Zwane Mwaikambo , "Theodore Ts'o" , Randy Dunlap , Dave Jones , Chuck Wolber , Chris Wedgwood , Michael Krufky , torvalds@osdl.org, akpm@osdl.org, Chuck Lever In-Reply-To: <20061012015306.GB27693@lists.us.dell.com> References: <20061010165621.394703368@quad.kroah.org> <20061010171429.GD6339@kroah.com> <1160610353.7015.8.camel@lade.trondhjem.org> <1160615547.20611.0.camel@localhost.localdomain> <1160616905.6596.14.camel@lade.trondhjem.org> <20061012015306.GB27693@lists.us.dell.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 12 Oct 2006 11:15:07 +0100 Message-Id: <1160648107.23731.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1784 Lines: 41 Ar Mer, 2006-10-11 am 20:53 -0500, ysgrifennodd Matt Domsch: > > > Then their hardware is faulty and should be specifically blacklisted not > > > make everyone have to deal with silly unmaintainable hacks. > > > > They are not hacks. The actual range of ports used by the RPC client is > > set using /proc/sys/sunrpc/(min|max)_resvport. People that don't have > > broken motherboards can override the default range, which is all that we > > are changing here. No.. you have it backwards. The tiny tiny number of people with broken boards can either set it themselves, use DMI, or ram the offending board somewhere dark belonging to whoever sold it to them > > To be fair, the motherboard manufacturers have actually registered these > > ports with IANA: This is irrelevant, they are stealing bits out of the incoming network stream. That's not just rude its dangerous - they should have their own MAC and IP stack for this. Port assignments are courtesy numbering to avoid collisions on your own stack. They have no more right to steal packets from that port than CERN does to claim all port 80 traffic on the internet. Why do I say dangerous - because they steal the data *before* your Linux firewalling and feed it to an unauditable binary firmware which has controlling access to large parts of the system without the OS even seeing it. Not a good idea IMHO on any box facing even a slightly insecure port. > For the one Dell server affected, we could DMI list > it; likewise for others. This should be done with DMI I agree. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/