On 08/12/2024 21:02, Malte Schröder wrote: > On 08/12/2024 02:23, Matthew Wilcox wrote: >> On Sun, Dec 08, 2024 at 12:01:11AM +0100, Malte Schröder wrote: >>> Reverting fb527fc1f36e252cd1f62a26be4906949e7708ff fixes the issue for >>> me. >> That's a merge commit ... does the problem reproduce if you run >> d1dfb5f52ffc? And if it does, can you bisect the problem any further >> back? I'd recommend also testing v6.12-rc1; if that's good, bisect >> between those two. >> >> If the problem doesn't show up with d1dfb5f52ffc? then we have a dilly >> of an interaction to debug ;-( > I spent half a day compiling kernels, but bisect was non-conclusive. > There are some steps where the failure mode changes slightly, so this is > hard. It ended up at 445d9f05fa149556422f7fdd52dacf487cc8e7be which is > the nfsd-6.13 merge ... > > d1dfb5f52ffc also shows the issue. I will try to narrow down from there. > > /Malte > Ha! This time I bisected from f03b296e8b51 to d1dfb5f52ffc. I ended up with 3b97c3652d91 as the culprit. /Malte
