From: Dan Carpenter <dan.carpenter@oracle.com>
To: cascardo@linux.vnet.ibm.com
Cc: netdev@vger.kernel.org
Subject: re: mlx4_en: fix endianness with blue frame support
Date: Tue, 18 Sep 2012 10:34:48 +0300 [thread overview]
Message-ID: <20120918073448.GA32445@elgon.mountain> (raw)
Hello Thadeu Lima de Souza Cascardo,
The patch c5d6136e10d6: "mlx4_en: fix endianness with blue frame
support" from Oct 10, 2011, leads to the following warning:
drivers/net/ethernet/mellanox/mlx4/en_tx.c:720 mlx4_en_xmit()
warn: potential memory corrupting cast. 4 vs 2 bytes
That patch introduced a call to cpu_to_be32() and added some endian
notation.
*(__be32 *) (&tx_desc->ctrl.vlan_tag) |= cpu_to_be32(ring->doorbell_qpn);
But it doesn't make sense because the data type is declared as u16 in
the header and we would be corrupting the next elements in the struct
which are ins_vlan and fence_size.
struct mlx4_wqe_ctrl_seg {
__be32 owner_opcode;
__be16 vlan_tag;
u8 ins_vlan;
u8 fence_size;
I guess the reason we get away with it is that the ->doorbell_qpn is
normally less that 65k. But doorbell_qpn is a u32 type so I think there
is a risk here.
regards,
dan carpenter
next reply other threads:[~2012-09-18 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 7:34 Dan Carpenter [this message]
2012-09-20 13:46 ` mlx4_en: fix endianness with blue frame support Or Gerlitz
2012-09-24 19:42 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120918073448.GA32445@elgon.mountain \
--to=dan.carpenter@oracle.com \
--cc=cascardo@linux.vnet.ibm.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox