From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: add anti-spoofing checks for 6to4 and 6rd
Date: Fri, 18 Jan 2013 14:32:00 -0500 (EST) [thread overview]
Message-ID: <20130118.143200.1013561317240911918.davem@davemloft.net> (raw)
In-Reply-To: <20130117200733.GA2055@order.stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Thu, 17 Jan 2013 21:07:33 +0100
> +#ifdef CONFIG_IPV6_SIT_6RD
> + if (ipv6_prefix_equal(addr6, &tunnel->ip6rd.prefix,
> + tunnel->ip6rd.prefixlen) &&
> + *addr != try_6rd(addr6, tunnel))
> + return 0;
> +#else
> + if (addr6->s6_addr16[0] == htons(0x2002) &&
> + *addr != try_6rd(addr6, tunnel))
> + return 0;
> +#endif
> + return 1;
> +}
...
> + } else if (!sit_chk_encap_addr(tunnel, &iph->saddr,
> + &ipv6_hdr(skb)->saddr) ||
> + !sit_chk_encap_addr(tunnel, &iph->daddr,
> + &ipv6_hdr(skb)->daddr)) {
None of these conditionals are indented properly, please fix this up.
Both conditionals and function calls that span multiple lines must use
the column after the openning parenthesis of the initial line as the
left justification of subsequent lines.
I see what you're doing, just using TAB characters exclusively to
ident, don't do that. You must use the appropriate combination of
TAB and space characters to achieve the correct indentaiton.
next prev parent reply other threads:[~2013-01-18 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 3:32 [PATCH] ipv6: add anti-spoofing checks for 6to4 and 6rd Hannes Frederic Sowa
2013-01-17 13:27 ` Hannes Frederic Sowa
2013-01-17 15:44 ` YOSHIFUJI Hideaki
2013-01-17 16:17 ` Hannes Frederic Sowa
2013-01-17 20:07 ` Hannes Frederic Sowa
2013-01-18 19:32 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-18 20:04 Hannes Frederic Sowa
2013-01-19 1:35 ` YOSHIFUJI Hideaki
2013-01-20 3:37 ` Hannes Frederic Sowa
2013-01-22 8:20 ` Hannes Frederic Sowa
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=20130118.143200.1013561317240911918.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.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 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).