All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom St Denis <tstdenis@elliptictech.com>
To: Mike Galbraith <bitbucket@online.de>
Cc: Eric Dumazet <erdnetdev@gmail.com>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
	David Miller <davem@davemloft.net>,
	steffen klassert <steffen.klassert@secunet.com>,
	herbert@gondor.hengli.com.au, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Michal Kubecek <mkubecek@suse.cz>
Subject: Re: IPsec AH use of ahash
Date: Sun, 20 Jan 2013 07:55:36 -0500 (EST)	[thread overview]
Message-ID: <1331637866.93068.1358686536347.JavaMail.root@elliptictech.com> (raw)
In-Reply-To: <1358658381.5743.44.camel@marge.simpson.net>



----- Original Message -----
> From: "Mike Galbraith" <bitbucket@online.de>
> To: "Tom St Denis" <tstdenis@elliptictech.com>
> Cc: "Eric Dumazet" <erdnetdev@gmail.com>, "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>, "David Miller"
> <davem@davemloft.net>, "steffen klassert" <steffen.klassert@secunet.com>, herbert@gondor.apana.org.au,
> linux-kernel@vger.kernel.org, netdev@vger.kernel.org, "Michal Kubecek" <mkubecek@suse.cz>
> Sent: Sunday, 20 January, 2013 12:06:21 AM
> Subject: Re: IPsec AH use of ahash
> 
> On Sat, 2013-01-19 at 05:30 -0500, Tom St Denis wrote:
> 
> > For those of us who do Kernel development during business hours
> > it's
> > hard to justify the work when the path to mainline is convoluted
> > and
> > landmined.
> 
> Sounds as though any patches you submit land on your dinner plate
> just
> like potatoes.  Hand the cook a pot of half peeled potatoes, he/she
> may
> say try again.  The result of a little extra effort is tastier taters
> for everybody feasting at the common table.. including you.

No, in reality what happened is the chef made potatos [incorrectly] got busy and asked others to help out and make more potatos.  Then came back and said ...

from ah4.c (which I copied into foo4.c to prove a point) ... that is currently in the kernel

WARNING: networking block comments put the trailing */ on a separate line
#94: FILE: net/ipv4/foo4.c:76:
+ * for validity, so paranoia is not required. */

ERROR: spaces required around that '<' (ctx:VxV)
#112: FILE: net/ipv4/foo4.c:94:
+		if (optlen<2 || optlen>l)
 		          ^

ERROR: spaces required around that '>' (ctx:VxV)
#112: FILE: net/ipv4/foo4.c:94:
+		if (optlen<2 || optlen>l)
 		                      ^

ERROR: do not use assignment in if condition
#180: FILE: net/ipv4/foo4.c:162:
+	if ((err = skb_cow_data(skb, 0, &trailer)) < 0)

WARNING: line over 80 characters
#223: FILE: net/ipv4/foo4.c:205:
+		ah->hdrlen  = (XFRM_ALIGN4(sizeof(*ah) + ahp->icv_trunc_len) >> 2) - 2;

WARNING: line over 80 characters
#225: FILE: net/ipv4/foo4.c:207:
+		ah->hdrlen  = (XFRM_ALIGN8(sizeof(*ah) + ahp->icv_trunc_len) >> 2) - 2;

ERROR: spaces required around that ':' (ctx:VxW)
#281: FILE: net/ipv4/foo4.c:263:
+	err = memcmp(icv, auth_data, ahp->icv_trunc_len) ? -EBADMSG: 0;
 	                                                           ^

WARNING: networking block comments put the trailing */ on a separate line
#337: FILE: net/ipv4/foo4.c:319:
+	 * so... Later this can change. */

ERROR: do not use assignment in if condition
#345: FILE: net/ipv4/foo4.c:327:
+	if ((err = skb_cow_data(skb, 0, &trailer)) < 0)

ERROR: spaces required around that ':' (ctx:VxW)
#395: FILE: net/ipv4/foo4.c:377:
+	err = memcmp(icv, auth_data, ahp->icv_trunc_len) ? -EBADMSG: 0;
 	                                                           ^

WARNING: space prohibited between function name and open parenthesis '('
#407: FILE: net/ipv4/foo4.c:389:
+	kfree (work_iph);

WARNING: line over 80 characters
#416: FILE: net/ipv4/foo4.c:398:
+	struct ip_auth_hdr *ah = (struct ip_auth_hdr *)(skb->data+(iph->ihl<<2));

WARNING: line over 80 characters
#429: FILE: net/ipv4/foo4.c:411:
+	x = xfrm_state_lookup(net, skb->mark, (const xfrm_address_t *)&iph->daddr,

WARNING: networking block comments don't use an empty /* line, use /* Comment...
#466: FILE: net/ipv4/foo4.c:448:
+
+	/*

ERROR: that open brace { should be on the previous line
#522: FILE: net/ipv4/foo4.c:504:
+static const struct xfrm_type ah_type =
+{

WARNING: please, no space before tabs
#525: FILE: net/ipv4/foo4.c:507:
+^I.proto^I     ^I= IPPROTO_AH,$

total: 7 errors, 9 warnings, 547 lines checked


So going back to my original point ... Had I upgraded AH4/AH6 to use AEAD you guys would have rejected it because of style issues too?

The maintainers are not MAINTAINING the code.  Then they call out sous-chef's that come by offering to contribute because the recipe is not being followed...

Tom



  parent reply	other threads:[~2013-01-20 12:55 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 16:51 IPsec AH use of ahash Tom St Denis
2013-01-16  6:21 ` Steffen Klassert
2013-01-18 19:35   ` Tom St Denis
2013-01-18 19:50     ` David Miller
2013-01-18 20:53       ` Tom St Denis
2013-01-18 22:16         ` Waskiewicz Jr, Peter P
2013-01-18 22:31           ` Tom St Denis
2013-01-19  2:33             ` Michal Kubecek
2013-01-19  2:59               ` Tom St Denis
2013-01-19  3:59               ` Eric Dumazet
2013-01-19 10:30                 ` Tom St Denis
2013-01-19 15:46                   ` Eric Dumazet
2013-01-20  5:06                   ` Mike Galbraith
2013-01-20 10:31                     ` Borislav Petkov
2013-01-20 12:56                       ` Tom St Denis
2013-01-20 13:34                         ` Alexander Holler
2013-01-20 13:54                           ` Tom St Denis
2013-01-30 22:16                             ` Jan Engelhardt
2013-01-20 22:07                         ` Steven Rostedt
2013-01-21  0:47                           ` Tom St Denis
2013-01-20 12:55                     ` Tom St Denis [this message]
2013-01-20 14:11                       ` Mike Galbraith
2013-01-20 15:07                         ` Tom St Denis
2013-01-20 16:34                           ` David Dillow
2013-01-20 17:40                             ` Tom St Denis
2013-01-20 18:11                               ` David Dillow
2013-01-20 18:47                                 ` Tom St Denis
2013-01-20 22:54                                   ` Steven Rostedt
2013-01-21  0:34                                     ` Borislav Petkov
2013-01-21  0:40                                       ` Tom St Denis
2013-01-21  1:08                                         ` Borislav Petkov
2013-01-21  9:18                                         ` David Dillow
2013-01-21 10:20                                           ` Tom St Denis
2013-01-21 13:38                                             ` Steven Rostedt
2013-01-21 13:45                                               ` Tom St Denis
2013-01-21 14:37                                                 ` Steven Rostedt
2013-01-21 14:51                                                   ` Tom St Denis
2013-01-21 15:28                                                     ` Steven Rostedt
2013-01-21 15:31                                                       ` Tom St Denis
2013-01-21 15:49                                                         ` Chris Friesen
2013-01-21 16:05                                                           ` Tom St Denis
2013-01-20 20:30                               ` Alan Cox
2013-01-21  0:46                                 ` Tom St Denis
2013-01-20 17:03                           ` H. Peter Anvin
2013-01-20 17:33                             ` Tom St Denis

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=1331637866.93068.1358686536347.JavaMail.root@elliptictech.com \
    --to=tstdenis@elliptictech.com \
    --cc=bitbucket@online.de \
    --cc=davem@davemloft.net \
    --cc=erdnetdev@gmail.com \
    --cc=herbert@gondor.hengli.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --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 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.