On Mon, Dec 11, 2023 at 08:29:06AM -0800, Suren Baghdasaryan wrote:
Just to rule out this possibility, linux-next was broken on Friday (see https://lore.kernel.org/all/CAJuCfpFiEqRO4qkFZbUCmGZy-n_ucqgR5NeyvnwXqYh+RU4...). I just checked and it's fixed now. Could you confirm that with the latest linux-next you still see the issue?
Yes, it looks like it's fixed today - thanks! (The fix was getting masked by the ongoing KVM breakage.)