[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <76jkxgubetbevbwbgq6onjwl4pu32bq3nrqmtj5zt23kkdculn@ez6bpprj2uan>
Date: Tue, 28 Jan 2025 11:13:03 +1100
From: Alistair Popple <apopple@...dia.com>
To: David Hildenbrand <david@...hat.com>
Cc: linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
nouveau@...ts.freedesktop.org, Karol Herbst <kherbst@...hat.com>, Lyude Paul <lyude@...hat.com>,
Danilo Krummrich <dakr@...nel.org>, David Airlie <airlied@...il.com>,
Simona Vetter <simona@...ll.ch>
Subject: Re: [PATCH v1 0/2] nouveau/svm: fix + cleanup for
nouveau_atomic_range_fault()
On Fri, Jan 24, 2025 at 07:15:22PM +0100, David Hildenbrand wrote:
> One fix and a minor cleanup.
>
> Only compile-tested due to lack of HW, so I'd be happy if someone with
> access to HW could test. But not sure how easy this is to trigger. Likely
> some concurrent MADV_DONTNEED on the PTE we just converted might be able
> to trigger it.
I have this setup so will certainly test it and see if I can trigger the bug
as well. Thanks for the fixes.
> Cc: Karol Herbst <kherbst@...hat.com>
> Cc: Lyude Paul <lyude@...hat.com>
> Cc: Danilo Krummrich <dakr@...nel.org>
> Cc: David Airlie <airlied@...il.com>
> Cc: Simona Vetter <simona@...ll.ch>
> Cc: Alistair Popple <apopple@...dia.com>
>
> David Hildenbrand (2):
> nouveau/svm: fix missing folio unlock + put after
> make_device_exclusive_range()
> nouveau/svm: don't initialize ret in nouveau_atomic_range_fault()
>
> drivers/gpu/drm/nouveau/nouveau_svm.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> --
> 2.47.1
>
Powered by blists - more mailing lists