From: Patrick McHardy <kaber@trash.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Joe Perches <joe@perches.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
Jeff Garzik <jeff@garzik.org>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] Fix infinite loop on dev_mc_unsync()
Date: Sat, 10 Nov 2007 00:12:34 +0100 [thread overview]
Message-ID: <4734E962.3010603@trash.net> (raw)
In-Reply-To: <20071109192033.GB22714@pogo>
Luis R. Rodriguez wrote:
> diff --git a/net/core/dev_mcast.c b/net/core/dev_mcast.c
> index 15241cf..2aea8e1 100644
> --- a/net/core/dev_mcast.c
> +++ b/net/core/dev_mcast.c
> @@ -160,14 +160,12 @@ EXPORT_SYMBOL(dev_mc_sync);
> */
> void dev_mc_unsync(struct net_device *to, struct net_device *from)
> {
> - struct dev_addr_list *da, *next;
> + struct dev_addr_list *da;
>
> netif_tx_lock_bh(from);
> netif_tx_lock_bh(to);
>
> - da = from->mc_list;
> - while (da != NULL) {
> - next = da->next;
> + for (da = from->mc_list; da; da = da->next) {
>
This may cause a use-after-free since __dev_addr_delete frees the address
when all references are gone.
> if (!da->da_synced)
> continue;
> __dev_addr_delete(&to->mc_list, &to->mc_count,
> @@ -175,7 +173,6 @@ void dev_mc_unsync(struct net_device *to, struct net_device *from)
> da->da_synced = 0;
> __dev_addr_delete(&from->mc_list, &from->mc_count,
> da->da_addr, da->da_addrlen, 0);
> - da = next;
> }
>
next prev parent reply other threads:[~2007-11-09 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 15:11 [PATCH] Fix infinite loop on dev_mc_unsync() Luis R. Rodriguez
2007-11-09 18:51 ` Luis R. Rodriguez
2007-11-09 19:07 ` Joe Perches
2007-11-09 19:21 ` Luis R. Rodriguez
2007-11-09 23:12 ` Patrick McHardy [this message]
[not found] ` <4734E962.3010603-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
2007-11-10 0:08 ` Joe Perches
2007-11-10 0:13 ` Patrick McHardy
[not found] ` <4734F7B6.7060505-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
2007-11-11 5:34 ` David Miller
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=4734E962.3010603@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--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).