Bug 1378320
| Summary: | [LIO target] libfc: lookup request for XID = 65535, indicates invalid CPU 7 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Bruno Goncalves <bgoncalv> | ||||
| Component: | kernel | Assignee: | Chris Leech <cleech> | ||||
| kernel sub component: | Storage Drivers | QA Contact: | Martin Hoyer <mhoyer> | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | unspecified | ||||||
| Priority: | unspecified | CC: | jpittman | ||||
| Version: | 7.3 | ||||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kernel-3.10.0-590.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-08-02 01:46:05 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1422628 | ||||||
| Attachments: |
|
||||||
|
Description
Bruno Goncalves
2016-09-22 06:45:08 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. Created attachment 1258556 [details]
posted patch
Patch(es) committed on kernel repository and an interim kernel build is undergoing testing Patch(es) available on kernel-3.10.0-590.el7 There are no more errors on FCoE target system after kernel update. No regression found. 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 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 |