netdev - Re: [PATCH net] mlx4_core: Do not map BF area if capability is 0

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20120220.192654.417785054157102848.davem@davemloft.net>
Date:	Mon, 20 Feb 2012 19:26:54 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	yevgenyp@...lanox.co.il
Cc:	netdev@...r.kernel.org, jackm@....mellanox.co.il
Subject: Re: [PATCH net] mlx4_core: Do not map BF area if capability is 0

From: Yevgeny Petrilin <yevgenyp@...lanox.co.il>
Date: Mon, 20 Feb 2012 09:38:52 +0200

> From: Jack Morgenstein <jackm@....mellanox.co.il>
> 
> BF can be disabled in some cases, the capability field, bf_reg_size is set
> to zero in this case. Don't map the BF area in this case, it would cause 
> failures.  In addition, leaving the BF area unmapped
> also alerts the ETH driver to not use BF.
> 
> Signed-off-by: Jack Morgenstein <jackm@....mellanox.co.il>

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