From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH net] packet: tpacket_v3: do not trigger bug() on wrong header status Date: Thu, 09 May 2013 20:32:52 +0200 Message-ID: <518BEBD4.5020003@redhat.com> References: <1367585820-2674-1-git-send-email-dborkman@redhat.com> <518968DF.9070008@redhat.com> <518AF306.8020307@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: David Miller , netdev , Jakub Zawadzki To: chetan loke Return-path: Received: from mx1.redhat.com ([209.132.183.28]:40149 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751257Ab3EISdB (ORCPT ); Thu, 9 May 2013 14:33:01 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On 05/09/2013 08:11 PM, chetan loke wrote: > On Wed, May 8, 2013 at 8:51 PM, Daniel Borkmann wrote: [..] > Normally people(sane code) will look for the return value from a > syscall. mmap is special because there's no syscall to run once you > mmap/setup the rings. Since there's no syscall there's no return > value. That's why we try to detect it at run-time and try to WARN the > user if we can. Well, I'm aware of all the internals and the problem statement. No need for further explanations. I also don't want to have endless, tiring discussions on netdev about a WARN_ON_ONCE statement either. I still don't like it for the reasons I stated ;-) but if you want to send a patch, I'm not going to stand in the way.