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
| ||
|
Date: Sat, 13 Apr 2013 13:09:16 +0200 From: Francois Romieu <romieu@...zoreil.com> To: Dmitry Kravkov <dmitry@...adcom.com> Cc: davem@...emloft.net, netdev@...r.kernel.org, eilong@...adcom.com Subject: Re: [PATCH net-next 1/4] bnx2x: refactor nvram read procedure Dmitry Kravkov <dmitry@...adcom.com> : > introduce a parameter to allow nvram read to return > data in BE or cpu order. [...] > @@ -1295,10 +1296,14 @@ static int bnx2x_nvram_read_dword(struct bnx2x *bp, u32 offset, __be32 *ret_val, > if (val & MCPR_NVM_COMMAND_DONE) { > val = REG_RD(bp, MCP_REG_MCPR_NVM_READ); > /* we read nvram data in cpu order > - * but ethtool sees it as an array of bytes > + * but ethtool uses it as an array of bytes > * converting to big-endian will do the work > + * if requested. You memcpy a u32 to an array of bytes instead of copying it byte after byte with proper shift operators and now you are paving the way for more endianess headaches. I'd rather avoid the memcpy when readying data for ethtool in the first place. Nit: the true/false method parameter style in middle layers is mildly readable when compared to usual _{be/le} kernel style (you should be able to avoid both almost completely anyway :o) ). -- Ueimor -- 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