netdev - Re: [PATCH 1/8] e1000: Convert boolean

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:	Tue, 18 Mar 2008 10:04:55 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Joe Perches <joe@...ches.com>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH 1/8] e1000: Convert boolean_t to bool

Joe Perches wrote:
> On Mon, 2008-03-17 at 10:12 -0700, Kok, Auke wrote:
>> Joe Perches wrote:
>>> On Mon, 2008-03-17 at 09:29 -0700, Auke Kok wrote:
>>>> On Thu, 2008-03-06 at 10:07 -0800, Kok, Auke wrote:
>>>>> send me a patch for e1000 and for ixgb and I'll happily apply those :)
>>> I gather you didn't run the little script to convert
>>> the u[_]*int\(8|16|32|64\) to u\1 uses? (u_int8_t -> u8, etc)
>>> Did you need or want actual patches to do that?
>> I'll take a patch for that and yes, I was too busy to do this myself just now :)
> 
> I just sent you a bunch of patches to do this conversion.
> 
> I started on doing a kind-of checkpatch/Lindent pass on e1000.
> 
> Some of the functions in e1000 are heavily indented
> and could be neatened with a little bit of rewrite.
> 
> For instance, here's a function in e1000_main.c
> 
> It's a little bit hard to understand with the indenting
> and breakup of the lines.  I think the rewrite below it
> is shorter and easier to read.
> 
> Do you want these sorts of changes too?

yeah absolutely

maybe this is a bit premature since we're going to have much more fun taking out
all the pci express code after 2.6.26 but we might as well start to queue this
stuff up now - at least I can keep it in a branch locally and this is exactly what
we need to do anyway

> static int
> e1000_transfer_dhcp_info(struct e1000_adapter *adapter, struct sk_buff *skb)
> {
> 	struct e1000_hw *hw =  &adapter->hw;
> 	u16 length, offset;
> 
> 	if (vlan_tx_tag_present(skb)) {
> 		if (!((vlan_tx_tag_get(skb) == adapter->hw.mng_cookie.vlan_id) &&
> 			( adapter->hw.mng_cookie.status &
> 			  E1000_MNG_DHCP_COOKIE_STATUS_VLAN_SUPPORT)) )
> 			return 0;
> 	}
> 	if (skb->len > MINIMUM_DHCP_PACKET_SIZE) {
> 		struct ethhdr *eth = (struct ethhdr *) skb->data;
> 		if ((htons(ETH_P_IP) == eth->h_proto)) {
> 			const struct iphdr *ip =
> 				(struct iphdr *)((u8 *)skb->data+14);
> 			if (IPPROTO_UDP == ip->protocol) {
> 				struct udphdr *udp =
> 					(struct udphdr *)((u8 *)ip +
> 						(ip->ihl << 2));
> 				if (ntohs(udp->dest) == 67) {
> 					offset = (u8 *)udp + 8 - skb->data;
> 					length = skb->len - offset;
> 
> 					return e1000_mng_write_dhcp_info(hw,
> 							(u8 *)udp + 8,
> 							length);
> 				}
> 			}
> 		}
> 	}
> 	return 0;
> }
> 
> could be:
> 
> static int e1000_transfer_dhcp_info(struct e1000_adapter *adapter,
> 				    struct sk_buff *skb)
> {
> 	struct e1000_hw *hw = &adapter->hw;
> 	struct ethhdr *eth;
> 	const struct iphdr *ip;
> 	struct udphdr *udp;
> 	u16 length, offset;
> 
> 	if (vlan_tx_tag_present(skb) &&
> 	    (!((vlan_tx_tag_get(skb) == adapter->hw.mng_cookie.vlan_id)
> 	       && (adapter->hw.mng_cookie.status
> 		   & E1000_MNG_DHCP_COOKIE_STATUS_VLAN_SUPPORT))))
> 		return 0;
> 	if (skb->len <= MINIMUM_DHCP_PACKET_SIZE)
> 		return 0;
> 	eth = (struct ethhdr *)skb->data;
> 	if (eth->h_proto != htons(ETH_P_IP))
> 		return 0;
> 	ip = (struct iphdr *)((u8 *)skb->data + 14);
> 	if (ip->protocol != IPPROTO_UDP)
> 		return 0;
> 	udp = (struct udphdr *)((u8 *)ip + (ip->ihl << 2));
> 	if (ntohs(udp->dest) != 67)
> 		return 0;
> 
> 	offset = (u8 *)udp + 8 - skb->data;
> 	length = skb->len - offset;
> 
> 	return e1000_mng_write_dhcp_info(hw, (u8 *)udp + 8, length);
> }

yeah, much better :)

--
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