linux-kernel - A problem about OX_ID reused by FCoE driver

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>] [day] [month] [year] [list]

Date:	Fri, 24 Jul 2015 11:52:38 +0800
From:	Rui Xiang <rui.xiang@...wei.com>
To:	<devel@...n-fcoe.org>
CC:	<linux-kernel@...r.kernel.org>, <wuyanjiang@...wei.com>,
	<jianghongbin@...wei.com>, <wick.wei@...wei.com>
Subject: A problem about OX_ID reused by FCoE driver

From: Wu Yanjiang <wuyanjiang@...wei.com>

Hi all,

On a system that was running 3.0.13-0.27-default, a problem that the OX_ID is reused by FCoE driver occurred. 
Which can be confirmed is that the problem is occurred at initiator side, but the reason how does it happen is unknown.

By the trace captured by JDSU protocol analyzer, the initiator initiated a read command about 10 seconds after 
the virtual link resumed . But about 10ms later, the initiator send ABTS to abort the read command. Then the 
OX_ID was reused for a new command immediately without abort response from target side and RRQ process.

Test environment ：
Initiator OS: SLES 11 SP2 (3.0.13-0.27-default)
Initiator CNA: INTEL X520-SR2

Test step：
1.INTEL X520-SR2 connect to intel 82599 card in target directly
2.Initiator initiates write and read command to target by FCoE VN2VN protect
3.Disconnect the physical link then reconnect it

Any advice is welcome.

Thanks.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/