From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: lorenzo@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: slightly simplify keeping IPv6 addresses on link down
Date: Fri, 10 Dec 2010 12:43:39 -0800 (PST) [thread overview]
Message-ID: <20101210.124339.242120993.davem@davemloft.net> (raw)
In-Reply-To: <20101201130421.0ac08bcd@nehalam>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 1 Dec 2010 13:04:21 -0800
> On Wed, 1 Dec 2010 12:52:42 -0800
> Lorenzo Colitti <lorenzo@google.com> wrote:
>
>> No, wait... The loop is protected by idev->lock, and the code just
>> before it that clears the temporary address list is essentially
>> identical (except it looks over tempaddr_list instead). Wouldn't that
>> blow up as well?
>
> The old code walked the list until it was empty. New code could
> get confused if list changed by other changes during the
> period when idev->lock is dropped and notifier is called.
I think Stephen has a point here.
You can't use a "_safe" list traversal if you are dropping the
lock in the middle of that traversal, which is what you code
will be doing.
Lorenzo you've already added serious bugs to this code with your
previous address handling changes (which had reference counting bugs),
so I'm going to heavily scrutinize any "cleanup" or other kind of
change you try to make here.
In fact I really wish you would just leave this code as-is instead
of trying to make such pointless tweaks to it.
Thanks.
next prev parent reply other threads:[~2010-12-10 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-26 18:06 [PATCH] ipv6: slightly simplify keeping IPv6 addresses on link down Lorenzo Colitti
2010-12-01 19:01 ` David Miller
2010-12-01 19:38 ` Lorenzo Colitti
2010-12-01 20:22 ` Stephen Hemminger
2010-12-01 20:52 ` Lorenzo Colitti
2010-12-01 21:04 ` Stephen Hemminger
2010-12-10 20:43 ` David Miller [this message]
2010-12-10 23:00 ` Lorenzo Colitti
2010-12-01 20:54 ` Lorenzo Colitti
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=20101210.124339.242120993.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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