From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH] tcp: Replace infinite loop on recvmsg bug with proper crashusers Date: Wed, 07 Nov 2012 08:29:12 -0800 Message-ID: <1352305752.3140.4449.camel@edumazet-glaptop> References: <1352247335-10396-1-git-send-email-jwerner@chromium.org> <20121107013907.GA31185@redhat.com> <20121107155434.GA17677@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Julius Werner , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Patrick McHardy , Hideaki YOSHIFUJI , James Morris , Alexey Kuznetsov , "David S. Miller" , Sameer Nanda , Mandeep Singh Baines , Eric Dumazet To: Dave Jones Return-path: In-Reply-To: <20121107155434.GA17677@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Wed, 2012-11-07 at 10:54 -0500, Dave Jones wrote: > It sounds more appropriate to me, instead of silently wedging the box. > At least with that approach we have a chance of finding out what happened. Its quite the opposite. If bug is still there 6 months after the commits that broke the drivers, (making an old bug visible) that means that people never realized the bug was there. I understand a distro maintainer has its own choices, but for upstream kernel we want to have early reports. This bug is fatal and a security issue. BUG() is appropriate. If the driver cant be fixed, it should be marked broken. So I personally NACKed patch to hide the bug, trying to be friendly to the user.