From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F17B5C433E0 for ; Mon, 8 Feb 2021 17:16:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AA33764E42 for ; Mon, 8 Feb 2021 17:16:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233725AbhBHRPu (ORCPT ); Mon, 8 Feb 2021 12:15:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234015AbhBHRP1 (ORCPT ); Mon, 8 Feb 2021 12:15:27 -0500 Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc [IPv6:2a0a:51c0:0:12e:520::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 02B39C061786; Mon, 8 Feb 2021 09:14:47 -0800 (PST) Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.92) (envelope-from ) id 1l9A7Y-0005Oo-Qd; Mon, 08 Feb 2021 18:14:44 +0100 Date: Mon, 8 Feb 2021 18:14:44 +0100 From: Florian Westphal To: Phil Sutter , Florian Westphal , Martin Gignac , netfilter@vger.kernel.org, netfilter-devel Subject: Re: Unable to create a chain called "trace" Message-ID: <20210208171444.GH16570@breakpoint.cc> References: <20210208154915.GF16570@breakpoint.cc> <20210208164750.GM3158@orbyte.nwl.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210208164750.GM3158@orbyte.nwl.cc> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org Phil Sutter wrote: > In general, shells eating the quotes is problematic and users may not be > aware of it. This includes scripts that mangle ruleset dumps by > accident, etc. (Not sure if it is really a problem as we quote some > strings already). > > Using JSON, there are no such limits, BTW. I really wonder if there's > really no fix for bison parser to make it "context aware". Right. We can probably make lots of keywords available for table/chain names by only recognizing them while parsing rules, i.e. via 'start conditions' in flex. But I don't think there is anyone with the time to do the needed scanner changes.