From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Khapyorsky Subject: Re: [PATCH] opensm/osm_slvl_map_rcv.c: verify port number values received from network Date: Sun, 3 Jan 2010 19:02:36 +0200 Message-ID: <20100103170236.GF26940@me> References: <20091201194110.GA26753@comcast.net> <20091229150528.GV26940@me> <20091229150735.GX26940@me> <20091230162745.GZ26940@me> <20091230194335.GB26940@me> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Hal Rosenstock Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-rdma@vger.kernel.org On 09:48 Thu 31 Dec , Hal Rosenstock wrote: > > I thought this was only done when these issues are actually found and > in general we are relying on compliance. OpenSM can rely on compliance in many cases, but it cannot crash (or become nonoperational in any other way) relying on compliance. > Is there a specific known > issue here ? > > If we are worrying about this as a general principle, there are more > places to bullet proof like this. Likely so and it would be good to fix all of them. > I am wondering about why the > exception here. It is not exception. I found this one, so fixed. Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html