From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft] rule: memleak in __do_add_setelems()
Date: Thu, 30 Apr 2020 17:46:29 +0200 [thread overview]
Message-ID: <20200430154629.GB3999@salvia> (raw)
In-Reply-To: <20200430154106.GO15009@orbyte.nwl.cc>
On Thu, Apr 30, 2020 at 05:41:06PM +0200, Phil Sutter wrote:
> [...]
> > I think I found the root cause:
> >
> > https://marc.info/?l=netfilter-devel&m=158825784609307&w=2
>
> Good catch!
I just pushed this out, thanks for reviewing.
prev parent reply other threads:[~2020-04-30 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 12:18 [PATCH nft] rule: memleak in __do_add_setelems() Pablo Neira Ayuso
2020-04-30 13:08 ` Pablo Neira Ayuso
2020-04-30 13:52 ` Phil Sutter
2020-04-30 14:47 ` Pablo Neira Ayuso
2020-04-30 15:41 ` Phil Sutter
2020-04-30 15:46 ` Pablo Neira Ayuso [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=20200430154629.GB3999@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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.