Hi Salvatore,
Can you check with current upstream kernels[…]
prior to getting into bisecting, I decided to give [1] a shot. From testing kernels available there I got this: OK: 6.1.112-1 BAD: 6.1.115-1 6.1.119-1 OK again: 6.3.1-1~exp1 current trixie current sid It may take some time until I get around to bisecting linux.git in the range 6.1.119..6.3.1 - what with real life and all.
Samewise, if you have the resources, can you bisect upstream versions between 6.1.112 and 6.1.115 specifically to identify which commit causes the regression?
That one was pretty easy to identify - the one which changes everything around in $ksrc/fs/udf (didn't write it up, though). However, I think the range I mentioned above is more interesting anyways, in terms of getting a viable patch together to fix this in bookworm.
Cheers Daniel [1] https://snapshot.debian.org/package/linux/
