From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id EE1103CB35 for ; Wed, 22 Aug 2018 05:25:39 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1534929938; bh=/EzrqCaiETKGI6CZYhyDOQBUkbF2k+g6ZGGTP12OwGo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=LuihZLW00WQS0xMxBy8PZAvfHPxzIUO47FSCw3iTRa8ObP8IJdhkNV8jA33M4Mxat FTUOE6+4eWBChBvsPPVecU/1YFFfhngkq6RBU0m9lWVW/nPFLOfn5RBZaO1fLMcCrw Yaf/XgZO6x6SU4tgMf2Fj/BAgKfVIMuWqBUAy4l7csPuhXqW93CPqG618XpWjdzJgR ehq9mDEeNhcoCrXoRNXOmWTpUmHECAw1Au/3y+5E6IRM9bAhTTLx8k4B3dxI0BW39Y RT0NCY4EOpYmhKhMvOt8dvt+4OML8ikIe0K2XdKhmcSMJnFHFN+zcX81Ho8CUkp9zb Fi8yDjaOPdvaw== To: Pete Heist , Dave Taht Cc: Cake List In-Reply-To: <5E9B5665-E115-4B8B-959A-0A4A4220046A@heistp.net> References: <20180816164423.14368-1-peterpenkov96@gmail.com> <20180816164423.14368-3-peterpenkov96@gmail.com> <5E9B5665-E115-4B8B-959A-0A4A4220046A@heistp.net> Date: Wed, 22 Aug 2018 11:25:37 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <871saqah2m.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Cake] [bpf-next RFC 2/3] flow_dissector: implements eBPF parser X-BeenThere: cake@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Cake - FQ_codel the next generation List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2018 09:25:40 -0000 Pete Heist writes: > The eBPF verifier seems fragile to me, where I=E2=80=99d be moving lines = of > code around and getting different error messages in an alien tongue. Well, it operates on the byte code and errs on the side of safety. I.e., if it can't prove your program is safe it is going to reject it. Which can be less than helpful. There's a mode where it can dump its state including the byte code it is operating at, which can be helpful in figuring out why you get an error. But it has a way to go yet compared with regular compiler error messages... :) -Toke