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] [day] [month] [year] [list]
Date:	Fri, 29 Nov 2013 15:42:28 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	therbert@...gle.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH v2 02/17] net: Add utility function to set the rxhash

From: Tom Herbert <therbert@...gle.com>
Date: Tue, 26 Nov 2013 09:22:34 -0800 (PST)

> @@ -703,6 +703,20 @@ unsigned int skb_find_text(struct sk_buff *skb, unsigned int from,
>  			   unsigned int to, struct ts_config *config,
>  			   struct ts_state *state);
>  
> +enum rxhash_types {
> +	RXHASH_TYPE_NONE,	/* Undefined type */
> +	RXHASH_TYPE_L2,		/* Uses L2 information (addresses) */
> +	RXHASH_TYPE_L3,		/* Uses L3 information */
> +	RXHASH_TYPE_L4,		/* Uses L4 information (ports) */
> +};
> +
> +static inline void
> +skb_set_rxhash(struct sk_buff *skb, __u32 hash, enum rxhash_types type)
> +{
> +	skb->l4_rxhash = (type == RXHASH_TYPE_L4);
> +	skb->rxhash = hash;
> +}

This looks fine but I want slightly more documentation in the
comments.

First of all, L2 is link layer "addresses" like ethernet, and L3 is
for protocol "addresses" such as for IPv4/IPv6.  Make this explicit
in the comments.

Next, answer the question "Does RXHASH_TYPE_LN imply
RXHASH_TYPE_L{N-1}?"

I suspect it's variable, so for example L4 implies L3, but not
necessarily L2.  Document this fully.

Finally, are there any serious negative consequences for not setting
the type correctly?  Or is it just a minor performance issue?  Either
way, document it.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ