From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 0/2] Sanitize two error conditions in netlink code
Date: Tue, 20 May 2025 12:53:55 +0200 [thread overview]
Message-ID: <aCxfQweTusR9IJM_@orbyte.nwl.cc> (raw)
In-Reply-To: <aCxa0jpNVApPQyLP@strlen.de>
On Tue, May 20, 2025 at 12:34:58PM +0200, Florian Westphal wrote:
> Phil Sutter <phil@nwl.cc> wrote:
> > While reviewing netlink deserialization code I noticed these two
> > potential issues. Submitting them separately from other work as they are
> > clear fixes (IMO).
>
> Thanks Phil, please push them out.
Series applied, thanks!
prev parent reply other threads:[~2025-05-20 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 18:25 [nft PATCH 0/2] Sanitize two error conditions in netlink code Phil Sutter
2025-05-16 18:25 ` [nft PATCH 1/2] netlink: Avoid potential NULL-ptr deref parsing set elem expressions Phil Sutter
2025-05-16 18:25 ` [nft PATCH 2/2] netlink: Catch unknown types when deserializing objects Phil Sutter
2025-05-20 10:34 ` [nft PATCH 0/2] Sanitize two error conditions in netlink code Florian Westphal
2025-05-20 10:53 ` 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=aCxfQweTusR9IJM_@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--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.