[adding Christian, the author of what appears to be the culprit] On 18.10.23 20:49, Jesse Hathaway wrote: > On Wed, Oct 18, 2023 at 1:40 PM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: FWIW, this thread afaics was supposed to be in reply to this submission: https://lore.kernel.org/all/20230712-vfs-chmod-symlinks-v1-1-27921df6011f@xxxxxxxxxx/ That patch later became 5d1f903f75a80d ("attr: block mode changes of symlinks") [v6.6-rc1, v6.5.5, v6.1.55, v5.4.257, v5.15.133, v5.10.197, v4.19.295, v4.14.326] >>> Unfortunately, this has not held up in LTSes without causing >>> regressions, specifically in crun: >>> >>> Crun issue and patch >>> 1. https://github.com/containers/crun/issues/1308 >>> 2. https://github.com/containers/crun/pull/1309 >> >> So thre's a fix already for this, they agree that symlinks shouldn't >> have modes, so what's the issue? > > The problem is that it breaks crun in Debian stable. They have fixed the > issue in crun, but that patch may not be backported to Debian's stable > version. In other words the patch seems to break existing software in > the wild. > >> It needs to reverted in Linus's tree first, otherwise you will hit the >> same problem when moving to a new kernel. > > Okay, I'll raise the issue on the linux kernel mailing list. Did you do that? I could not find anything. Just wondering, as right now there is still some time to fix this regression before 6.6 is released (and then the fix can be backported to the stable trees, too). Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.
