From: Jeremy Sowden <jeremy@azazel.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH ulogd2 2/4] filter: fix buffer sizes in filter plug-ins
Date: Thu, 8 Dec 2022 21:21:38 +0000 [thread overview]
Message-ID: <Y5JVYhDHRnxeSEvB@azazel.net> (raw)
In-Reply-To: <Y5JSFbQVlHUbMMM/@salvia>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On 2022-12-08, at 22:07:33 +0100, Pablo Neira Ayuso wrote:
> On Sat, Dec 03, 2022 at 07:02:10PM +0000, Jeremy Sowden wrote:
> [...]
> > The arrays are indexed by subtracting `START_KEY` from the enum
> > value of the key currently being processed: `hwmac_str[okey -
> > START_KEY]`. However, this means that the last key (`KEY_MAC_ADDR`
> > in this example) will run off the end of the array. Increase the
> > size of the arrays.
>
> BTW, did you detect this via valgrind or such? If so, posting an
> extract of the splat in the commit message is good to have.
One of the GCC sanitizers, IIRC. I'll make sure to include a trace in
future.
J.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-08 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 19:02 [PATCH ulogd2 0/4] Some bug-fixes Jeremy Sowden
2022-12-03 19:02 ` [PATCH ulogd2 1/4] ulogd: fix parse-error check Jeremy Sowden
2022-12-03 19:02 ` [PATCH ulogd2 2/4] filter: fix buffer sizes in filter plug-ins Jeremy Sowden
2022-12-08 21:07 ` Pablo Neira Ayuso
2022-12-08 21:21 ` Jeremy Sowden [this message]
2022-12-03 19:02 ` [PATCH ulogd2 3/4] JSON: remove incorrect config value check Jeremy Sowden
2022-12-03 19:02 ` [PATCH ulogd2 4/4] db: fix back-log capacity checks Jeremy Sowden
2022-12-08 20:58 ` [PATCH ulogd2 0/4] Some bug-fixes Pablo Neira Ayuso
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=Y5JVYhDHRnxeSEvB@azazel.net \
--to=jeremy@azazel.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 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.