From: Andrew Lunn Subject: Re: [PATCH net-next v5 20/20] net: WireGuard secure network tunnel Date: Wed, 19 Sep 2018 14:38:53 +0200 Message-ID: <20180919123853.GC26940@lunn.ch> References: <20180918161646.19105-1-Jason@zx2c4.com> <20180918161646.19105-21-Jason@zx2c4.com> <20180918233411.GB17466@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: LKML , Netdev , Linux Crypto Mailing List , David Miller , Greg Kroah-Hartman To: "Jason A. Donenfeld" Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On Wed, Sep 19, 2018 at 04:04:01AM +0200, Jason A. Donenfeld wrote: > Hi Andrew, > > On Wed, Sep 19, 2018 at 1:34 AM Andrew Lunn wrote: > > I see this BUG_ON() is still here. It really needs to be removed. It > > does not look like you need to crash the kernel here. Can you add in a > > test of len >= 128, do a WARN and then return. I think you then leak > > some memory, but i would much prefer that to a crashed machine. > > Sure, I'll change it to that. Great, thanks. I noticed there is at least one more BUG() statements. It would be good to remove them all. BUG() should only be used when something bad has already happened and we want to minimise the damage by killing the machine immediately. Andrew