On 2024-01-08 15:13, Greg KH wrote:
That's interesting, there's a different cifs report that says a different commit was the issue: https://lore.kernel.org/r/ZZhrpNJ3zxMR8wcU@xxxxxxxxxxx is that the same as this one?
It looks like a different issue. The linked report claims that the problem was introduced in 6.1.69 by a different commit, but both Jan Čermák and I don't experience anything wrong with 6.1.69. Jan Čermák found commit bef4315f19ba6f434054f58b958c0cf058c7a43f via bisection and compiled a kernel that reverts it, and the problem stopped manifesting.
