lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1294004772.5675.11.camel@wall-e>
Date:	Sun, 02 Jan 2011 22:46:12 +0100
From:	Stefani Seibold <stefani@...bold.net>
To:	Jesper Juhl <jj@...osbits.net>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	davem@...emloft.net, netdev@...r.kernel.org,
	eric.dumazet@...il.com, shemminger@...tta.com
Subject: Re: [PATCH] new UDPCP Communication Protocol

Am Sonntag, den 02.01.2011, 20:55 +0100 schrieb Jesper Juhl:
> On Sun, 2 Jan 2011, stefani@...bold.net wrote:


> > +
> > +#define VERSION	"0.71"
> 
> I personally don't think this makes much sense.
> Version numbers for individual modules tend to not get updated as the code 
> changes over the years, which make them rather meaningless.
> Since this module depends on functionallity of the kernel which it is 
> compiled with, the actual (meaningful) version of this code is that of the 
> kernel tree being compiled that includes this code. Which again makes this 
> specific version define meaningless.
> 
> So, why not save a few lines of code and get rid of this rather pointless 
> thing?
> 

I like it, it gives me a better monitoring during development which
version is currently tested.

> [...]
> > +static struct udpcp_dest *find_dest(struct sock *sk, __be32 addr, __be16 port)
> > +{
> > +	struct udpcp_dest *dest;
> > +
> > +	dest = __find_dest(sk, addr, port);
> 
> Why not
> 
> static struct udpcp_dest *find_dest(struct sock *sk, __be32 addr, __be16 port)
> {
>      struct udpcp_dest *dest =  __find_dest(sk, addr, port);
> 
> ?
I will fix it but i think this is counting peas.
 
> 
> 
> [...]
> > + * Release a routing table entry if no packed will be assembled
> 
> Don't you mean "packet" rather than "packed" here?
> 
> 
Right.

> [...]
> > + * Return true it the passed skb socket buffer is the last in the list
> 
> I believe you mean "Return true if the passed ..."
> 
Right.

> 
> [...]
> > +static void udpcp_flush_err(struct sock *sk, struct udpcp_dest *dest)
> > +{
> > +	struct inet_sock *inet = inet_sk(sk);
> > +	struct udpcp_sock *usk = udpcp_sk(sk);
> > +
> > +	if (!inet->recverr)
> > +		skb_queue_purge(&dest->xmit);
> > +	else {
> 
> CodingStyle would want this as
> 
>      if (!inet->recverr) {
>              skb_queue_purge(&dest->xmit);
>      } else {
> 
> If one branch needs {} then both should get them.
> 
./scripts/checkpatch.pl did not complain about this, so i think it is
okay.

> 
> [...]
> > +	if (!dest->xmit_last)
> > +		_udpcp_xmit(sk, dest);
> > +	else {
> > +		skb = dest->xmit_wait;
> 
> Same comment as above.
> There are more occurences of this, I'm not going to point them all out.
> 
> 
> [...]
> > +static inline void udpcp_release_sock(struct sock *sk)
> > +{
> > +	struct udpcp_sock *usk = udpcp_sk(sk);
> > +
> > +	while (usk->timeout)
> > +		udpcp_handle_timeout(sk);
> > +	release_sock(sk);
> > +        check_timeout(sk);
> 
> The line above uses spaces for indentation. It should use one tab.
> 
> 
> [...]
> > +static unsigned int udpcp_tx_queue_len(struct sock *sk, struct udpcp_dest *dest)
> > +{
> > +	struct sk_buff *skb;
> > +	unsigned int n;
> > +
> > +	n = 0;
> 
> Might as well save a few lines and make this
> 
> static unsigned int udpcp_tx_queue_len(struct sock *sk, struct udpcp_dest *dest)
> {
>      struct sk_buff *skb;
>      unsigned int n = 0;
> 
> 
> [...]
> > +static unsigned int udpcp_rx_queue_len(struct sock *sk, struct udpcp_dest *dest)
> > +{
> > +	struct sk_buff *skb;
> > +	unsigned int n;
> > +
> > +	n = 0;
> 
> Here as well
>         unsigned int n = 0;
> 
> 

I fix it in the next release.

Thanks


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ