From: Phil Sutter <phil@nwl.cc>
To: josh lant <joshualant@googlemail.com>
Cc: netfilter-devel@vger.kernel.org, josh lant <joshualant@gmail.com>
Subject: Re: iptables- accessing unallocated memory
Date: Fri, 5 Jul 2024 18:43:11 +0200 [thread overview]
Message-ID: <Zoginy1sxVHnhbNy@orbyte.nwl.cc> (raw)
In-Reply-To: <CAMQRqN+S6487boLi98hGSe-X9-8aM1XkNS+BRb+dMS+4hGiBhA@mail.gmail.com>
On Fri, Jul 05, 2024 at 04:56:28PM +0100, josh lant wrote:
> > Could you please try with current HEAD of iptables? I think the bug you
> > see was fixed by commit 2026b08bce7fe ("nft: ruleparse: Add missing
> > braces around ternary"). At least I don't see a problem in
> > testcases/iptables/0002-verbose-output_0 when testing with either
> > valgrind or ASAN.
> >
>
> I was unable to build from master due to some other issue, but I
> applied this patch to 1.8.10 and now all the tests that were failing
> with segfaults are working...
>
> Many thanks for your quick response. Have a nice weekend!
You're welcome! Glad the blind squirrel found another nut. ;)
Cheers, Phil
prev parent reply other threads:[~2024-07-05 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 13:47 iptables- accessing unallocated memory josh lant
2024-07-05 15:28 ` Phil Sutter
2024-07-05 15:56 ` josh lant
2024-07-05 16:43 ` 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=Zoginy1sxVHnhbNy@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=joshualant@gmail.com \
--cc=joshualant@googlemail.com \
--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