From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: pioppo@ferrara.linux.it
Cc: davem@redhat.com, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org, usagi@linux-ipv6.org
Subject: Re: [PATCH] IPv6: Don't assign a same IPv6 address on a same interface (is Re: IPv6 duplicate address bugfix)
Date: Mon, 31 Mar 2003 03:35:24 +0900 (JST) [thread overview]
Message-ID: <20030331.033524.114862210.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20030330163656.GA18645@ferrara.linux.it>
In article <20030330163656.GA18645@ferrara.linux.it> (at Sun, 30 Mar 2003 18:36:56 +0200), Simone Piunno <pioppo@ferrara.linux.it> says:
> Because everywhere else in the file {read,write}_lock_bh() is used
> instead of {read,write}_lock(), so I'm assuming that _bh is required
> but I really don't know why.
maybe.
> - locking inside ipv6_add_addr() is simpler and more linear but
> semantically wrong because you're unable to tell the user why his
> "ip addr add" failed. E.g. you answer ENOBUFS instead of EEXIST.
We don't want to create duplicate address in any case.
ipv6_add_addr() IS right place.
And, we can return error code by using IS_ERR() etc.
I'll fix this.
> - your ipv6_chk_same_addr() does a useless check for (dev != NULL)
>
> > +static
> > +int ipv6_chk_same_addr(const struct in6_addr *addr, struct net_device *dev)
> > +{
> > + struct inet6_ifaddr * ifp;
> > + u8 hash = ipv6_addr_hash(addr);
> > +
> > + read_lock_bh(&addrconf_hash_lock);
> > + for(ifp = inet6_addr_lst[hash]; ifp; ifp=ifp->lst_next) {
> > + if (ipv6_addr_cmp(&ifp->addr, addr) == 0) {
> > + if (dev != NULL && ifp->idev->dev == dev)
> > break;
> > }
>
> your never "break" if dev == NULL, so you could return 0 before
> even acquiring the lock.
It is not a problem because dev is always non-NULL.
However, it should be dev == NULL || ifp->idev->dev == dev.
Thanks.
(I don't understand what you mean by "you could return 0
before even acquiring the lock.")
--
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
next prev parent reply other threads:[~2003-03-30 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-30 12:27 IPv6 duplicate address bugfix Simone Piunno
2003-03-30 13:08 ` (usagi-users 02296) " YOSHIFUJI Hideaki / 吉藤英明
2003-03-30 14:58 ` [PATCH] IPv6: Don't assign a same IPv6 address on a same interface (is Re: IPv6 duplicate address bugfix) YOSHIFUJI Hideaki / 吉藤英明
2003-03-30 16:36 ` Simone Piunno
2003-03-30 18:35 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2003-03-31 1:34 ` [PATCH] IPv6: Don't assign a same IPv6 address on a same interface YOSHIFUJI Hideaki / 吉藤英明
2003-03-31 19:05 ` David S. Miller
2003-03-31 18:23 ` (usagi-users 02296) IPv6 duplicate address bugfix Peter Bieringer
2003-03-31 18:56 ` [ds6-devel] " Simone Piunno
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=20030331.033524.114862210.yoshfuji@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pioppo@ferrara.linux.it \
--cc=usagi@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
all inboxes | Powered by JetHome®