From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
netdev@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Wei Wang <weiwan@google.com>, David Miller <davem@davemloft.net>,
msizanoen1 <msizanoen@qtmlabs.xyz>,
stable@vger.kernel.org
Subject: Re: [PATCH net] ipv6: fix memory leak in fib6_rule_suppress
Date: Wed, 24 Nov 2021 08:00:38 +0100 [thread overview]
Message-ID: <YZ3jFik9MNi8m6JV@kroah.com> (raw)
In-Reply-To: <20211123200347.597e2daf@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Tue, Nov 23, 2021 at 08:03:47PM -0800, Jakub Kicinski wrote:
> On Tue, 23 Nov 2021 13:48:32 +0100 Jason A. Donenfeld wrote:
> > The original author of this commit and commit message is anonymous and
> > is therefore unable to sign off on it. Greg suggested that I do the sign
> > off, extracting it from the bugzilla entry above, and post it properly.
> > The patch "seems to work" on first glance, but I haven't looked deeply
> > at it yet and therefore it doesn't have my Reviewed-by, even though I'm
> > submitting this patch on the author's behalf. And it should probably get
> > a good look from the v6 fib folks. The original author should be on this
> > thread to address issues that come off, and I'll shephard additional
> > versions that he has.
>
> Does the fact that the author responded to the patch undermine the need
> for this special handling?
Unless the author wishes to use their real name, sadly it does not :(
prev parent reply other threads:[~2021-11-24 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 12:48 [PATCH net] ipv6: fix memory leak in fib6_rule_suppress Jason A. Donenfeld
2021-11-23 12:57 ` msizanoen
2021-11-24 4:03 ` Jakub Kicinski
2021-11-24 7:00 ` Greg Kroah-Hartman [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=YZ3jFik9MNi8m6JV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=kuba@kernel.org \
--cc=msizanoen@qtmlabs.xyz \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=weiwan@google.com \
/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).