Bug 1378320 - [LIO target] libfc: lookup request for XID = 65535, indicates invalid CPU 7
Summary: [LIO target] libfc: lookup request for XID = 65535, indicates invalid CPU 7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Chris Leech
QA Contact: Martin Hoyer
URL:
Whiteboard:
Depends On:
Blocks: 1422628
TreeView+ depends on / blocked
 
Reported: 2016-09-22 06:45 UTC by Bruno Goncalves
Modified: 2021-09-06 13:18 UTC (History)
1 user (show)

Fixed In Version: kernel-3.10.0-590.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-02 01:46:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
posted patch (1.83 KB, patch)
2017-02-28 23:58 UTC, Chris Leech 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1842 0 normal SHIPPED_LIVE Important: kernel security, bug fix, and enhancement update 2017-08-01 18:22:09 UTC

Description Bruno Goncalves 2016-09-22 06:45:08 UTC 
Description of problem:
When a FCoE initiator connects to FCoE target this message appear several times and then they keep being show from time to time on FCoE target.

[260869.893050] fc_exch_find: 3 callbacks suppressed
[260869.916964] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260869.950810] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260869.986441] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260870.024911] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260870.065903] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260870.099080] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260870.132267] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260870.165661] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260870.165783] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260870.231764] libfc: lookup request for XID = 65535, indicates invalid CPU 7
[260875.008779] fc_exch_find: 448 callbacks suppressed
[260875.033460] libfc: lookup request for XID = 65535, indicates invalid CPU 7
...

Version-Release number of selected component (if applicable):
Kernel 3.10.0-506.el7

How reproducible:
100%

Steps to Reproduce:
1.Configure LIO FCoE target
2.Connect an FCoE initiator to it
3.Check for the messages on FCoE target
Comment 3 Chris Leech 2016-10-18 18:50:06 UTC 
The XID sanity check I added for bz#1190204 bz#1351356 didn't take into account that exchange lookups are attempted even for the reserved value of 0xffff (65535) that indicates an exchange originated by the other endpoint that we haven't assigned a responder ID to yet.  Rare case for an initiator, but normal operating behaviour for a target.

I'll get that cleaned up.
Comment 4 Chris Leech 2017-02-28 23:58:51 UTC 
Created attachment 1258556 [details]
posted patch
Comment 5 Rafael Aquini 2017-03-08 00:09:38 UTC 
Patch(es) committed on kernel repository and an interim kernel build is undergoing testing
Comment 7 Rafael Aquini 2017-03-08 21:47:08 UTC 
Patch(es) available on kernel-3.10.0-590.el7
Comment 9 Martin Hoyer 2017-06-05 07:24:30 UTC 
There are no more errors on FCoE target system after kernel update.
No regression found.
Comment 11 errata-xmlrpc 2017-08-02 01:46:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1842
Comment 12 errata-xmlrpc 2017-08-02 02:20:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1842
Note You need to log in before you can comment on or make changes to this bug.