From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Pirko Subject: Re: [patch net-next 1/2 v3] tc: add BPF based action Date: Wed, 14 Jan 2015 16:55:07 +0100 Message-ID: <20150114155507.GC1869@nanopsycho.orion> References: <1421229297-14473-1-git-send-email-jiri@resnulli.us> <54B66F08.2010305@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Daniel Borkmann , Network Development , "David S. Miller" , Jamal Hadi Salim , Hannes Frederic Sowa To: Alexei Starovoitov Return-path: Received: from mail-wg0-f50.google.com ([74.125.82.50]:50144 "EHLO mail-wg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751182AbbANPzT (ORCPT ); Wed, 14 Jan 2015 10:55:19 -0500 Received: by mail-wg0-f50.google.com with SMTP id a1so9715383wgh.9 for ; Wed, 14 Jan 2015 07:55:17 -0800 (PST) Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: Wed, Jan 14, 2015 at 04:39:34PM CET, ast@plumgrid.com wrote: >On Wed, Jan 14, 2015 at 5:28 AM, Daniel Borkmann wrote: >> >> I'm still wondering about the drop semantics ... wouldn't it be more >> intuitive to use 0 for drops in this context? > >good point. >I think it must be 0 to match behavior of socket filters, etc. >If program tries to access beyond packet size or does divide >by zero if will be terminated and will return 0. >So zero should be the safest action from caller point of view. Will do. Thanks!