You are not logged in.
I upgraded my kernel yesterday from 6.16.1-arch1-1 to 6.16.2-arch1-1 and noticed that when I try to get an extended attribute over NFS, it just gives me:
getxattr: Operation not supportedI tried the LTS kernel as well (6.12.43-1) and it also suffers the problem. Downgrading back to 6.16.1-arch1-1 restores functionality; also, alpine linux doesn't have the same problem, so it's definitely the linux kernel builds.
I don't have an account on the gitlab so I can't file a proper bug about this, tragically.
Offline
I don't have an account on the gitlab so I can't file a proper bug about this, tragically.
Follow the instruction on the red banner at the top https://gitlab.archlinux.org/archlinux to register.
Offline
scott_fakename wrote:I don't have an account on the gitlab so I can't file a proper bug about this, tragically.
Follow the instruction on the red banner at the top https://gitlab.archlinux.org/archlinux to register.
Yeah...
Anyway I looked at the kernel configs between the two and there's nothing different but the version in the comment up top.
$ diff -u 6.16.*.config
--- 6.16.1-arch1-1.config 2025-08-23 11:05:18.395938793 -0700
+++ 6.16.2-arch1-1.config 2025-08-23 11:05:18.636940329 -0700
@@ -1,6 +1,6 @@
#
# Automatically generated file; DO NOT EDIT.
-# Linux/x86 6.16.1-arch1 Kernel Configuration
+# Linux/x86 6.16.2-arch1 Kernel Configuration
#
CONFIG_CC_VERSION_TEXT="gcc (GCC) 15.2.1 20250813"
CONFIG_CC_IS_GCC=ySo it smells like an upstream kernel issue and not arch's fault.
Offline
Do you need help with the bisection between 6.16.1 and 6.16.2?
Offline
No, it took me a bit to figure out a way to build it with makepkg but using a local git repo but i have something going; I bet there's a less janky way than i'm doing but it's building so far.
Offline
Bisect says this one broke it. I will figure out what I need to do later; it's been a long day.
Offline
Usual process would be see if you can cleanly revert that commit from 6.16.2 as a cross check the bisection result is accurate.
Assuming it is if it is also broken in the latest mainline release candidate:
sudo pacman -U https://pkgbuild.com/\~gromit/linux-bisection-kernels/linux-mainline-6.17rc2-1-x86_64.pkg.tar.zstThen report it by replying to https://lore.kernel.org/linux-nfs/488da … space.com/ (instructions are in the link)
If it only effects stable then report it by replying to https://lore.kernel.org/stable/20250818 … ation.org/
You could also report in on the kernel bugzilla but that will probably be slower.
Edit:
Thank You for reporting https://lore.kernel.org/linux-nfs/528e7 … gmail.com/
Last edited by loqs (2025-08-29 13:49:46)
Offline