From: David Miller <davem@davemloft.net>
To: kumaran.4353@gmail.com
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net IPv6]: Fix maximum IPv6 address limit violation
Date: Mon, 07 Apr 2014 15:06:11 -0400 (EDT) [thread overview]
Message-ID: <20140407.150611.1998010372710875030.davem@davemloft.net> (raw)
In-Reply-To: <533FEE9B.5090806@gmail.com>
From: Balakumaran Kannan <kumaran.4353@gmail.com>
Date: Sat, 05 Apr 2014 17:22:59 +0530
> +#ifdef CONFIG_IPV6_PRIVACY
> + /* When IPv6 privacy extension is enabled, there must
> + * be two IPv6 address slots available.
> + * - One for MAC based address
> + * - Another for temporary address
> + */
> + if (max_addresses > 1)
> + max_addresses--;
> +#endif
> if (!max_addresses ||
> ipv6_count_addresses(in6_dev) < max_addresses)
> ifp = ipv6_add_addr(in6_dev, &addr, NULL,
> --
> 1.7.9.5
>
Your claim is that you're shooting for accurate policy enforcement, but even
you patch doesn't do this.
You are not taking into account whether temporary addresses will even be
created.
An accurate implementation would duplicate all of the special checks that
manage_tempaddrs() does to determine whether a temporary address will be
created or not. In particular, it needs to check if the device is even
configured to use tempaddrs.
prev parent reply other threads:[~2014-04-07 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 11:52 [PATCH net IPv6]: Fix maximum IPv6 address limit violation Balakumaran Kannan
2014-04-05 19:35 ` Hannes Frederic Sowa
2014-04-06 6:27 ` Balakumaran Kannan
2014-04-07 19:06 ` David Miller [this message]
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=20140407.150611.1998010372710875030.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kumaran.4353@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.