[17.04 FEAT] Integrate kernel message catalogue for s390x into Ubuntu distribution

[bugproxy]

For each kernel a message catalogue is available for s390x.
For better servicablity, customers asking for having this kernel messages as part of the distribution.

[Dimitri John Ledkov (xnox)]

Incorrect package name. Please blacklist "kernel-package" in the bugproxy bridge.

[Dimitri John Ledkov (xnox)]

Please open new bug against "linux" package.

[Frank Heimes (fheimes)]

Please add a public link to the patch and message catalogue - thx.

[Dimitri John Ledkov (xnox)]

Ideally a public git repository that the kernel team may pull from.

Said git repository should be kept up to date w.r.t. upstream linus rc releases & stable point release.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2016-11-11 06:43 EDT-------
Latest msg catalogue can be found for kernel 4.7
http://www.ibm.com/developerworks/linux/linux390/kernel-4.7.html#message-catalog

[Dimitri John Ledkov (xnox)]

Ubuntu yakkety and zesty are on 4.8, patch for 4.7 does apply albeit with fuzz.
The fact that it's behind a captive portal, prevents automating pulling/rebasing this patch.
Can you please publish a git tree for the message catalog on github.com, launchpad.net, kernel.org?

[bugproxy (bugproxy)]

------- Comment on attachment From <email address hidden> 2017-01-16 06:29 EDT-------

Attached msg catalogue for kernel 4.10. Even the kernel is finalized, this package is really near the final one, for early integration and testing.

[Tim Gardner (timg-tpi)]

Heinz - can I get this as a regular git patch with proper provenance ?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-01-17 03:26 EDT-------
Tim - the msg catalogue will be provided via developerworks, like all the other kernel contributions for s390x.
As an example please see here for kernel 4.8.
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html

[Tim Gardner (timg-tpi)]

I cannot include patches that have no provenance and require EULA assent from the download web page.

[bugproxy (bugproxy)]

------- Comment on attachment From <email address hidden> 2017-01-17 08:51 EDT-------

There is no git commit. Therefore this should be used as s-o-b

[Dimitri John Ledkov (xnox)]

If there is no public repository, it will cause conflicts when merging and preparing new kernel releases.

Please provide public git repository which is rebased on devel rc milestones, starting from -rc1. Because canonical kernel team starts integration of new kernels from -rc1. Previously the "developerworks" downloads where severely out of date. And e.g. 4.9 catalog was not public until well after the final release.

The benefit of this patch is also dubious. It may be well known to s390x users; but not to the generic Linux users who are starting to use s390x. Have you considered contributing regular kernel manpages and documentation upstream instead of changing the codepaths that affect all architectures?

I'm inclined to reject applying the message catalog patch, as it will be a maintainance burden on the canonical kernel team delaying kernel maintainance and the -rc rebases, whilst providing little overall benefit. But it's up to the kernel team to accept/reject this patch/feature.

[Tim Gardner (timg-tpi)]

Committed to the unstable kernel (v4.10-rc4)

[Dimitri John Ledkov (xnox)]

@rtg

Please check if http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/log/?h=kernel-messages suitable to pull the kernel-messages from. Please note, it may require repulls with later milestones (e.g. rc4 or later).

[Tim Gardner (timg-tpi)]

This kernel-messages branch needs to be refactored for v4.10-rc6 as it does not cherry-pick cleanly.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-02-02 06:03 EDT-------
Rebased the kernel-message branch on kernel.org to 4.10-rc6. This applied with a simple 'git am' without any hickups.

[Tim Gardner (timg-tpi)]

Oops, I had already applied a previous kernel-messages commit which is why the commit at the top of your branch would not apply. I've now cherry-picked from the v4.10-rc6 version and pushed to unstable (which will soon become Zesty 17.04).

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 4.10.0-8.10

---------------
linux (4.10.0-8.10) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
    - LP: #1664217

  * [Hyper-V] Bug fixes for storvsc (tagged queuing, error conditions)
    (LP: #1663687)
    - scsi: storvsc: Enable tracking of queue depth
    - scsi: storvsc: Remove the restriction on max segment size
    - scsi: storvsc: Enable multi-queue support
    - scsi: storvsc: use tagged SRB requests if supported by the device
    - scsi: storvsc: properly handle SRB_ERROR when sense message is present
    - scsi: storvsc: properly set residual data length on errors

  * Ubuntu16.10-KVM:Big configuration with multiple guests running SRIOV VFs
    caused KVM host hung and all KVM guests down. (LP: #1651248)
    - KVM: PPC: Book 3S: XICS cleanup: remove XICS_RM_REJECT
    - KVM: PPC: Book 3S: XICS: correct the real mode ICP rejecting counter
    - KVM: PPC: Book 3S: XICS: Fix potential issue with duplicate IRQ resends
    - KVM: PPC: Book 3S: XICS: Implement ICS P/Q states
    - KVM: PPC: Book 3S: XICS: Don't lock twice when checking for resend

  * overlay: mkdir fails if directory exists in lowerdir in a user namespace
    (LP: #1531747)
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1575 (LP: #1534961)
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * CVE-2016-1576 (LP: #1535150)
    - SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs

  * Miscellaneous Ubuntu changes
    - SAUCE: md/raid6 algorithms: scale test duration for speedier boots
    - SAUCE: Import aufs driver
    - d-i: Build message-modules udeb for arm64
    - rebase to v4.10-rc8

  * Miscellaneous upstream changes
    - Revert "UBUNTU: SAUCE: aufs -- remove .readlink assignment"
    - Revert "UBUNTU: SAUCE: (no-up) aufs: for v4.9-rc1, support setattr_prepare()"
    - Revert "UBUNTU: SAUCE: aufs -- Add flags argument to aufs_rename()"
    - Revert "UBUNTU: SAUCE: aufs -- Convert to use xattr handlers"
    - Revert "UBUNTU: SAUCE: Import aufs driver"

  [ Upstream Kernel Changes ]

  * rebase to v4.10-rc8

 -- Tim Gardner <email address hidden> Mon, 06 Feb 2017 08:34:24 -0700

[bugproxy (bugproxy)]

For each kernel a message catalogue is available for s390x.
For better servicablity, customers asking for having this kernel messages as part of the distribution.

Incorrect package name. Please blacklist "kernel-package" in the bugproxy bridge.

Please open new bug against "linux" package.

Please add a public link to the patch and message catalogue - thx.

Ideally a public git repository that the kernel team may pull from.

Said git repository should be kept up to date w.r.t. upstream linus rc releases & stable point release.
Latest msg catalogue can be found for kernel 4.7
http://www.ibm.com/developerworks/linux/linux390/kernel-4.7.html#message-catalog

Ubuntu yakkety and zesty are on 4.8, patch for 4.7 does apply albeit with fuzz.
The fact that it's behind a captive portal, prevents automating pulling/rebasing this patch.
Can you please publish a git tree for the message catalog on github.com, launchpad.net, kernel.org?

Heinz - can I get this as a regular git patch with proper provenance ?
Tim - the msg catalogue will be provided via developerworks, like all the other kernel contributions for s390x.
As an example please see here for kernel 4.8.
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html

I cannot include patches that have no provenance and require EULA assent from the download web page.

If there is no public repository, it will cause conflicts when merging and preparing new kernel releases.

Please provide public git repository which is rebased on devel rc milestones, starting from -rc1. Because canonical kernel team starts integration of new kernels from -rc1. Previously the "developerworks" downloads where severely out of date. And e.g. 4.9 catalog was not public until well after the final release.

The benefit of this patch is also dubious. It may be well known to s390x users; but not to the generic Linux users who are starting to use s390x. Have you considered contributing regular kernel manpages and documentation upstream instead of changing the codepaths that affect all architectures?

I'm inclined to reject applying the message catalog patch, as it will be a maintainance burden on the canonical kernel team delaying kernel maintainance and the -rc rebases, whilst providing little overall benefit. But it's up to the kernel team to accept/reject this patch/feature.

Committed to the unstable kernel (v4.10-rc4)

@rtg

Please check if http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/log/?h=kernel-messages suitable to pull the kernel-messages from. Please note, it may require repulls with later milestones (e.g. rc4 or later).

This kernel-messages branch needs to be refactored for v4.10-rc6 as it does not cherry-pick cleanly.
Rebased the kernel-message branch on kernel.org to 4.10-rc6. This applied with a simple 'git am' without any hickups.

Oops, I had already applied a previous kernel-messages commit which is why the commit at the top of your branch would not apply. I've now cherry-picked from the v4.10-rc6 version and pushed to unstable (which will soon become Zesty 17.04).

This bug was fixed in the package linux - 4.10.0-8.10

---------------
linux (4.10.0-8.10) zesty; urgency=low

[ Tim Gardner ]

*...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-04-19 10:36 EDT-------
IBM Bugzilla Status -> Closed ; available with GA version