So

>> 1/ inode numbers will be seen to have changed between kernel versions.
>>    32-bit arches will see large inode numbers now instead of the hashed
>>    ones they saw before.
>>

That seems fine to me. This is all during runtime only, and doesn't
change ondisk format at all right?


>> 2/ any really old software not built with LFS support may start failing
>>    stat() calls with -EOVERFLOW on inode numbers >2^32. Nothing much we
>>    can do about these, but hopefully the intersection of people running
>>    such code on ceph will be very small.

I think we universally support LFS even on armhf & i386 arches. Also
note the https://lintian.debian.org/tags/binary-file-built-without-LFS-
support.html

It may have been better to scope the patch for backport to s390x only,
however, given that hwe kernels will have this eventually, imho it is
fine to submit this.

Btw, you can also submit kernel patch to the kernel-team mailing list,
if it is formatted as per Ubuntu Kernel team guidelines with like
BugLink: https://bugs.launchpad.net/bugs/1899582.

Note we are past kernel freeze now, and there is no SRU cycle between
now and 8th of November, due to datacenter move as announced in
https://lists.ubuntu.com/archives/kernel-sru-
announce/2020-September/000170.html Hence the earlier this can land is
probably December.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899582

Title:
  ceph: fix inode number handling on arches with 32-bit ino_t

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1899582/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to