From: Florian Westphal <fw@strlen.de>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: netfilter-devel@vger.kernel.org, Phil Sutter <phil@nwl.cc>
Subject: Re: pipapo with element shadowing, wildcard support
Date: Wed, 3 Dec 2025 18:25:11 +0100 [thread overview]
Message-ID: <aTBydxPbKZnh-iUw@strlen.de> (raw)
In-Reply-To: <20251203150849.0ea16d5f@elisabeth>
Stefano Brivio <sbrivio@redhat.com> wrote:
> > Question would be if it makes sense to relax the -EEXIST checks so that in
> > step 1 the wider key could be inserted first and then allow it to be
> > (partially) shadowed later.
>
> The reason why I implemented it this way was to avoid possible
> ambiguity because entries inserted first are anyway matched first.
> Details with example at:
>
> https://lore.kernel.org/all/20200226115924.461f2029@redhat.com/
Thanks.
> It might make sense to change that, but that's not entirely trivial as
> you would need to renumber / reorder entries in the buckets on
> insertion, so that more specific entries are always added first.
Right, it needs a reorder step.
> I guess you assumed this was already implemented, which is a reasonable
> assumption, but unfortunately I didn't add that, it looked good enough
> as it was, back then.
No, I realized this was missing, the -EEXIST tests would not have
made sense otherwise.
What I did not know if it was omitted due to 'not feasible/too hard' or
'good enough for now'.
> See that same thread for some discussion about it, in particular around:
>
> https://lore.kernel.org/all/20200225184857.GC9532@orbyte.nwl.cc/
>
> other than that I'm not aware of previous discussions.
Thanks for the pointer!
next prev parent reply other threads:[~2025-12-03 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 15:21 pipapo with element shadowing, wildcard support Florian Westphal
2025-12-03 14:08 ` Stefano Brivio
2025-12-03 17:25 ` Florian Westphal [this message]
2025-12-23 12:23 ` Stefano Brivio
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=aTBydxPbKZnh-iUw@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=sbrivio@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.