kernel: tolerate LPAR clock offsets

Bug #1644505 reported by bugproxy
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Skipper Bug Screeners
Xenial
Fix Released
Medium
Tim Gardner
Yakkety
Fix Released
Undecided
Unassigned
Zesty
Fix Released
Undecided
Skipper Bug Screeners

Bug Description

Bugzilla for fix integration.

Please backport:
Upstream git commits for the LPAR offset handling:

9dc06ccf4699db81 "s390/time: move PTFF definitions"
4027789192d14967 "s390/time: LPAR offset handling"

bugproxy (bugproxy)
tags: added: architecture-s39064 bugnameltc-149054 severity-high targetmilestone-inin---
Changed in ubuntu:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
affects: ubuntu → kernel-package (Ubuntu)
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

kernel-package shall never be used. please blacklist, or remap to "linux".

information type: Public → Private
bugproxy (bugproxy)
tags: added: targetmilestone-inin16041
removed: targetmilestone-inin---
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-11-24 08:21 EDT-------
Upstream git commits for the LPAR offset handling:

9dc06ccf4699db81 "s390/time: move PTFF definitions"
4027789192d14967 "s390/time: LPAR offset handling"

Frank Heimes (fheimes)
affects: kernel-package (Ubuntu) → linux (Ubuntu)
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Zesty & Yakkety have v4.8 already. Xenial has linux-hwe-edge kernel at v4.8 as well.

description: updated
Changed in linux (Ubuntu Zesty):
status: New → Fix Released
Changed in linux (Ubuntu Yakkety):
status: New → Fix Released
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Please consider submitting this patch to v4.4.y stable trees.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Patches are public, may this bug marked as public too for the SRU or should a separate public bug be opened for this?

Changed in linux (Ubuntu Xenial):
status: New → Confirmed
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
importance: Undecided → Medium
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Confirmed
Frank Heimes (fheimes)
information type: Private → Public
Revision history for this message
Tim Gardner (timg-tpi) wrote :
Changed in linux (Ubuntu Xenial):
assignee: Canonical Kernel Team (canonical-kernel-team) → Tim Gardner (timg-tpi)
status: Confirmed → In Progress
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Confirmed → In Progress
Luis Henriques (henrix)
Changed in linux (Ubuntu Xenial):
status: In Progress → Fix Committed
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: In Progress → Fix Committed
Luis Henriques (henrix)
Changed in linux (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2017-01-11 07:14 EDT-------
IBM Bugzilla -> closed

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.