From: Eric Dumazet <eric.dumazet@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv6: Initialize the neighbour pointer of rt6_info on allocation
Date: Thu, 05 Jul 2012 17:16:44 +0200 [thread overview]
Message-ID: <1341501404.2583.4267.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120705131828.GE1869@secunet.com>
On Thu, 2012-07-05 at 15:18 +0200, Steffen Klassert wrote:
> git commit 97cac082 (ipv6: Store route neighbour in rt6_info struct)
> added a neighbour pointer to rt6_info. Currently we don't initialize
> this pointer at allocation time. We assume this pointer to be valid
> if it is not a null pointer, so initialize it on allocation.
>
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
> ---
> net/ipv6/route.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index ceff71d..6cc6c88 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -273,7 +273,7 @@ static inline struct rt6_info *ip6_dst_alloc(struct net *net,
> 0, 0, flags);
>
> if (rt) {
> - memset(&rt->rt6i_table, 0,
> + memset(&rt->n, 0,
> sizeof(*rt) - sizeof(struct dst_entry));
> rt6_init_peer(rt, table ? &table->tb6_peers : net->ipv6.peers);
> }
Hmm, could we find a way to avoid this for future changes ?
We know dst_entry is the first field, so maybe :
if (rt) {
struct dst_entry *dst = (struct dst_entry *)rt;
memset(dst + 1, 0, sizeof(*rt) - sizeof(*dst));
next prev parent reply other threads:[~2012-07-05 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 13:18 [PATCH net-next] ipv6: Initialize the neighbour pointer of rt6_info on allocation Steffen Klassert
2012-07-05 15:16 ` Eric Dumazet [this message]
2012-07-06 6:54 ` Steffen Klassert
2012-07-06 9:16 ` Steffen Klassert
2012-07-05 21:21 ` 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=1341501404.2583.4267.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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