[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201125162532.1299794-1-daniel.vetter@ffwll.ch>
Date: Wed, 25 Nov 2020 17:25:28 +0100
From: Daniel Vetter <daniel.vetter@...ll.ch>
To: DRI Development <dri-devel@...ts.freedesktop.org>
Cc: Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
linux-mm@...ck.org, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Daniel Vetter <daniel.vetter@...ll.ch>
Subject: [PATCH v4 0/3] mmu_notifier vs fs_reclaim lockdep annotations
Hi all,
Just resending with the polish applied, no functional changes at all.
Previous versions.
v3: https://lore.kernel.org/dri-devel/20201120095445.1195585-1-daniel.vetter@ffwll.ch/
v2: https://lore.kernel.org/dri-devel/20200610194101.1668038-1-daniel.vetter@ffwll.ch/
Changes since v3:
- more acks/r-b
- typos in the kerneldoc fixed
Changes since v2:
- Now hopefully the bug that bombed xfs fixed.
- With unit-tests (that's the part I really wanted and never got to)
- might_alloc() helper thrown in for good.
I think if we have an ack/review from fs-devel this should be good to
land. Last version that landed in -mm (v2) broke xfs pretty badly.
Unfortuantely I don't have a working email from Qian anymore, who reported
the xfs issue. Maybe Dave Chinner instead?
Cheers, Daniel
Daniel Vetter (3):
mm: Track mmu notifiers in fs_reclaim_acquire/release
mm: Extract might_alloc() debug check
locking/selftests: Add testcases for fs_reclaim
include/linux/sched/mm.h | 16 ++++++++++++++
lib/locking-selftest.c | 47 ++++++++++++++++++++++++++++++++++++++++
mm/mmu_notifier.c | 7 ------
mm/page_alloc.c | 31 ++++++++++++++++----------
mm/slab.h | 5 +----
mm/slob.c | 6 ++---
6 files changed, 86 insertions(+), 26 deletions(-)
--
2.29.2
Powered by blists - more mailing lists