From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Usha Srinivasan
<usha.srinivasan-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ib receive completion error
Date: Wed, 10 Nov 2010 11:34:48 +0200 [thread overview]
Message-ID: <4CDA6738.1030409@voltaire.com> (raw)
In-Reply-To: <7866DA1F8D2D4541B87FEE88E633ABAA2BBE305046-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
Usha Srinivasan wrote:
> Can someone from Mellanox tell me what the vendor error 0x32 means? I am getting this error for wc.opcode 128 (IB_WC_RECV) wc.status 4 (IB_WC_LOC_PROT_ERR). I am running ofed 1.5.2 and am getting it on both rhel5 and sles11
>
You can't count on the wc.opcode when the status isn't success (0), and
yes, we're also saw tons on "ib0: failed recv event status=4, wrid=154
vend_err 32)" errors when running iscsi/tcp over IPoIB stress from
windows client to linux node acting as the iscsi target and using ofed
1.5.2, it starts to look like DoS attack is possible here.
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-10 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 19:22 ib receive completion error Usha Srinivasan
[not found] ` <7866DA1F8D2D4541B87FEE88E633ABAA2BBE305046-amwN6d8PyQWXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2010-11-10 9:34 ` Or Gerlitz [this message]
[not found] ` <4CDA70C0.8050003@mellanox.co.il>
[not found] ` <4CDA70C0.8050003-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2010-11-10 10:16 ` Tziporet Koren
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=4CDA6738.1030409@voltaire.com \
--to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=usha.srinivasan-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.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