From: Ben Greear <greearb@candelatech.com>
To: Patrick McHardy <kaber@trash.net>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [MACVLAN]: Fix memleak on device removal/crash on module removal
Date: Wed, 07 May 2008 15:03:19 -0700 [thread overview]
Message-ID: <48222727.2090606@candelatech.com> (raw)
In-Reply-To: <48215DAC.1070704@trash.net>
Patrick McHardy wrote:
>
> ------------------------------------------------------------------------
>
> commit 2fe876e51d1f053b55d8d50c3733b136b6add016
> Author: Patrick McHardy <kaber@trash.net>
> Date: Wed May 7 09:43:05 2008 +0200
>
> [MACVLAN]: Fix memleak on device removal/crash on module removal
Thanks. I just tested this on 2.6.23 and it seems to fix the crash.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2008-05-07 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 7:43 [MACVLAN]: Fix memleak on device removal/crash on module removal Patrick McHardy
2008-05-07 22:03 ` Ben Greear [this message]
2008-05-07 22:45 ` David Miller
2008-05-08 8:14 ` David Miller
2008-05-08 15:27 ` Ben Greear
2008-05-08 15:34 ` Patrick McHardy
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=48222727.2090606@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.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).