ceph -- Unable to mount ceph volume on s390x

Default Comment by Bridge

Default Comment by Bridge

Hi, was the attached patch already brought to upstream's attention?
Please provide a github ticket (PR/issues) - so far I/we couldn't find one.
Please notice that we want to avoid handling out-of-tree patches - thx.

Oh, just noticed that this is a kernel issue and fix.
In this case we need of course an upstream accepted kernel patch.
I didn't found anything like "ceph: fix up endian bug in managing feature bits" in linux-next yet.
Is it available at some staging tree?

------- Comment From <email address hidden> 2020-04-29 17:30 EDT-------
(In reply to comment #12)
> Oh, just noticed that this is a kernel issue and fix.
> In this case we need of course an upstream accepted kernel patch.
> I didn't found anything like "ceph: fix up endian bug in managing feature
> bits" in linux-next yet.
> Is it available at some staging tree?

Hi, It was queued for Linux-5.7-rcX (don't look for this in staging trees):
https://marc.info/?l=ceph-devel&m=158817653611155&w=2

------- Comment From <email address hidden> 2020-05-08 13:56 EDT-------
It was accepted today. Will be in Linux-5.7-rc5

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb24fdd8e6f5c6bb95129748a1801c6476492aba

Thanks Eduard,
found it in linux-next, could cleanly cherry-pick and compile it.
And it's coming just in time for the SRU cycle - perfect!

Kernel SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2020-May/thread.html#109710
Updating status to 'In Progress'.

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

------- Comment From <email address hidden> 2020-05-20 04:25 EDT-------
Hi,

IIUC, if this patch requires cephadm/ceph-container to do the testing as I understand from Eduard, then it's not ready today unfortunately, it's still WIP. I wonder if we can still bootstrap the cluster manually as we have been doing in the past months.

------- Comment From <email address hidden> 2020-05-20 06:53 EDT-------
@Canonical, Comment #10 is not preciseliy correct. IBM will verify the fix soon..

------- Comment From <email address hidden> 2020-05-25 11:40 EDT-------
Hi,

As of today the kernel 5.4.0.33.37-38 in focal-proposed doesn't seem to have this patch pulled in.

It seems it was only pulled in master-next branch this morning :
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/fs/ceph?h=master-next&id=f86b72f1b8b399e456e84151f3bfe0ad7cabe29d

Talked briefly with Frank on IRC, Frank also thinks that the patch didn't make it. He is helping on this. Thanks Frank.

------- Comment From <email address hidden> 2020-05-25 11:54 EDT-------
So 5.4.0-34.38 (only 34.37 kernel images and meta package linux-generic=33.38 were available before) was just tagged few minutes ago from master-next to include this patch.
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=Ubuntu-5.4.0-34.38&id=dc6c325dcb0c741ce4e70d0091dca3f610cbcb3f

Quote from Frank on IRC:
jfh> so the kernel that incl. the ceph patch and is supposed to be in proposed right now, needed to be re-spun due to a regression
<jfh> the the next kernel that will come -34 will have the ceph patch included
<jfh> indeed a special case

Will test again as soon as new kernel get built. Thanks.

@kernel-team and @ubuntu-archive just for clarification: the 'verification-failed-focal' tag was only set because the kernel in proposed that should have the patch that is mentioned here included, needed to be revoked due to a regression and the kernel used for the verification didn't had it in.
So the verification was not possible, rather than failed.

@Tuan, would you be able to verify this LP ticket again?
The patch should be included in the kernel that is currently in proposed (the re-spin was done).
Thx

------- Comment From <email address hidden> 2020-06-08 04:21 EDT-------
It seems to work now with 5.4.0-34.38 being the latest in focal-proposed.
Thanks Frank.

Hi Tuan, thx for re-verifying on short notice!

This bug was fixed in the package linux - 5.4.0-37.41

---------------
linux (5.4.0-37.41) focal; urgency=medium

  * CVE-2020-0543
    - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
    - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
    - SAUCE: x86/cpu: Add 'table' argument to cpu_matches()
    - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
      mitigation
    - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation
    - SAUCE: x86/speculation: Add Ivy Bridge to affected list

 -- Marcelo Henrique Cerri <email address hidden> Wed, 03 Jun 2020 11:24:23 -0300

All autopkgtests for the newly accepted linux-oracle-5.4 (5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

This bug was fixed in the package linux - 5.4.0-42.46

---------------
linux (5.4.0-42.46) focal; urgency=medium

  * focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)

  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
    - SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

linux (5.4.0-41.45) focal; urgency=medium

  * focal/linux: 5.4.0-41.45 -proposed tracker (LP: #1885855)

  * Packaging resync (LP: #1786013)
    - update dkms package versions

  * CVE-2019-19642
    - kernel/relay.c: handle alloc_percpu returning NULL in relay_open

  * CVE-2019-16089
    - SAUCE: nbd_genl_status: null check for nla_nest_start

  * CVE-2020-11935
    - aufs: do not call i_readcount_inc()

  * ip_defrag.sh in net from ubuntu_kernel_selftests failed with 5.0 / 5.3 / 5.4
    kernel (LP: #1826848)
    - selftests: net: ip_defrag: ignore EPERM

  * Update lockdown patches (LP: #1884159)
    - SAUCE: acpi: disallow loading configfs acpi tables when locked down

  * seccomp_bpf fails on powerpc (LP: #1885757)
    - SAUCE: selftests/seccomp: fix ptrace tests on powerpc

  * Introduce the new NVIDIA 418-server and 440-server series, and update the
    current NVIDIA drivers (LP: #1881137)
    - [packaging] add signed modules for the 418-server and the 440-server
      flavours

 -- Khalid Elmously <email address hidden> Thu, 09 Jul 2020 19:50:26 -0400

------- Comment From <email address hidden> 2020-07-28 03:40 EDT-------
IBM bugzilla status-> closed, Fix Relased with 20.04