netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH ebtables-nft] nft-bridge: work around recent "among" decode breakage
Date: Wed, 30 Nov 2022 15:20:55 +0100	[thread overview]
Message-ID: <Y4dmx55r32Z5yH0E@orbyte.nwl.cc> (raw)
In-Reply-To: <20221130103812.67033-1-fw@strlen.de>

On Wed, Nov 30, 2022 at 11:38:12AM +0100, Florian Westphal wrote:
> ebtables-nft-save will fail with
> "unknown meta key" when decoding "among" emulation with ipv4 or ipv6
> addresses included.
> 
> This is because "meta protocol ip" is used as a dependency, but
> its never decoded anywhere.
> 
> Skip this for now to restore the "ebtables/0006-flush_0"
> test case.
> 
> Fixes: 25883ce88bfb ("nft: check for unknown meta keys")
> Signed-off-by: Florian Westphal <fw@strlen.de>

Best-effort approach. :)

Acked-by: Phil Sutter <phil@nwl.cc>

      reply	other threads:[~2022-11-30 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30 10:38 [PATCH ebtables-nft] nft-bridge: work around recent "among" decode breakage Florian Westphal
2022-11-30 14:20 ` Phil Sutter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y4dmx55r32Z5yH0E@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).