From: "David S. Miller" <davem@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: willy@w.ods.org, netdev@oss.sgi.com, jgarzik@pobox.com,
Alexandre.Cassen@wanadoo.fr
Subject: Re: Deadlock problem with dev->refcnt somewhere in netlink/multicast... [PATCH]
Date: Mon, 2 Feb 2004 15:47:55 -0800 [thread overview]
Message-ID: <20040202154755.311745d1.davem@redhat.com> (raw)
In-Reply-To: <OFDBAB37F5.227951E9-ON88256E2E.0080F5BF@us.ibm.com>
On Mon, 2 Feb 2004 16:41:11 -0700
David Stevens <dlstevens@us.ibm.com> wrote:
> Below is a patch for the reference count problem you ran into.
>
> The problem is that the IGMP code was using "IFF_UP" to determine
> if a report should be sent or a timer should be started. But it is not
> necessarily cleared during a destroy_dev.
>
> The IPv4 code was also missing an ip_mc_down() call added in the
> IPv6 code for a similar case by Jan Oravec.
Applied to both 2.4.x and 2.6.x, thanks David.
next prev parent reply other threads:[~2004-02-02 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 23:41 Deadlock problem with dev->refcnt somewhere in netlink/multicast... [PATCH] David Stevens
2004-02-02 23:47 ` David S. Miller [this message]
2004-02-03 6:00 ` Willy Tarreau
2004-02-05 18:21 ` Willy Tarreau
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=20040202154755.311745d1.davem@redhat.com \
--to=davem@redhat.com \
--cc=Alexandre.Cassen@wanadoo.fr \
--cc=dlstevens@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=willy@w.ods.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).