From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Fernando Fernandez Mancera <fmancera@suse.de>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft v2] support for afl++ (american fuzzy lop++) fuzzer
Date: Tue, 21 Oct 2025 00:24:05 +0200 [thread overview]
Message-ID: <aPa2hTdpyAb1y57R@calendula> (raw)
In-Reply-To: <aPa1wsoHHKjZ89hG@strlen.de>
On Tue, Oct 21, 2025 at 12:20:50AM +0200, Florian Westphal wrote:
> Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > > > Can this be controlled from control plane instead?
> > >
> > > Oh well, you refer to the patch that checks this from control plane.
> > >
> > > I remember an issue with abort path, has this been addressed?
> >
> > I think this does not handle rule/set element removal with jump/goto
> > correctly.
>
> I haven't reviewed it yet. There are buildbot warning reports and
> submitter seems to have abandoned this patch set.
>
> I will review and toss it if needed, this bug exists forever so its
> not like we must apply this right away.
>
> If absolutely needed i can scrape time next month to work on this.
I think this is also broken from commit path, when two tables are
validated, first succeeds then the second table fails. Leaving the
first table with incorrect jump count.
next prev parent reply other threads:[~2025-10-20 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 11:51 [PATCH nft v2] support for afl++ (american fuzzy lop++) fuzzer Florian Westphal
2025-10-19 9:34 ` Fernando Fernandez Mancera
2025-10-19 14:17 ` Florian Westphal
2025-10-20 14:11 ` Fernando Fernandez Mancera
2025-10-20 14:24 ` Florian Westphal
2025-10-20 15:23 ` Fernando Fernandez Mancera
2025-10-20 18:35 ` Pablo Neira Ayuso
2025-10-20 19:07 ` Pablo Neira Ayuso
2025-10-20 21:48 ` Pablo Neira Ayuso
2025-10-20 22:20 ` Florian Westphal
2025-10-20 22:24 ` Pablo Neira Ayuso [this message]
2025-10-20 22:46 ` Florian Westphal
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=aPa2hTdpyAb1y57R@calendula \
--to=pablo@netfilter.org \
--cc=fmancera@suse.de \
--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).