netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH 2.6.9]: Fix netdevice/inet6_dev reference leaks in ip6_route_add error paths
Date: Wed, 20 Oct 2004 22:17:08 -0700	[thread overview]
Message-ID: <20041020221708.46689319.davem@davemloft.net> (raw)
In-Reply-To: <417591A2.4090201@trash.net>

On Wed, 20 Oct 2004 00:13:54 +0200
Patrick McHardy <kaber@trash.net> wrote:

> The recent changes to ip6_route_add added multiple leaks in
> error paths. This patch should fix them.

Applied already, as mentioned in my response to Yoshifuji-san's
ACK of this patch.

      parent reply	other threads:[~2004-10-21  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 22:13 [PATCH 2.6.9]: Fix netdevice/inet6_dev reference leaks in ip6_route_add error paths Patrick McHardy
2004-10-20  6:35 ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-21  4:22   ` David S. Miller
2004-10-21  5:17 ` David S. Miller [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=20041020221708.46689319.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=netdev@oss.sgi.com \
    --cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).