[19.04 FEAT] Splitting DIF and DIX boot time controls
Bug #1814537 reported by
bugproxy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu on IBM z Systems |
Fix Released
|
High
|
Frank Heimes | ||
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Skipper Bug Screeners | ||
Bug Description
Functions:
A Linux on Z user can separately configure DIF and DIF+DIX integrity protection mechanisms.
Business Value:
Customers can improve data integrity protection for data stored on FCP storage by making use of hardware-based DIF data integrity checking between FCP channel and target LUN. Previously, this feature could only be enabled together with the DIX feature that has proven to be too unstable for production usage.
Will be made available with kernel 5.0
| tags: | added: architecture-s39064 bugnameltc-175239 severity-high targetmilestone-inin1904 |
| Changed in ubuntu: | |
| assignee: | nobody → Skipper Bug Screeners (skipper-screen-team) |
| affects: | ubuntu → linux (Ubuntu) |
Revision history for this message
| Frank Heimes (fheimes) wrote | #1 |
| Changed in ubuntu-z-systems: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Frank Heimes (frank-heimes) |
| status: | Triaged → Incomplete |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #2 |
Revision history for this message
| Frank Heimes (fheimes) wrote | #3 |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Fix Committed |
| Changed in ubuntu-z-systems: | |
| status: | Incomplete → Fix Committed |
Revision history for this message
| Frank Heimes (fheimes) wrote | #4 |
| Changed in linux (Ubuntu): | |
| status: | Fix Committed → Fix Released |
| Changed in ubuntu-z-systems: | |
| status: | Fix Committed → Fix Released |
| information type: | Private → Public |
Revision history for this message
| bugproxy (bugproxy) wrote | #5 |
To post a comment you must log in.
Since the target kernel of disco/19.04 is still 4.21 aka 5.0 this should land automatically. Hence not assigning this ticket to anyone, but just verifying, once target kernel got released ...