From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-xfs@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/3] mmu_notifier fs fs_reclaim lockdep annotations
Date: Fri, 20 Nov 2020 10:54:41 +0100 [thread overview]
Message-ID: <20201120095445.1195585-1-daniel.vetter@ffwll.ch> (raw)
Hi all,
I've finally gotten around to polish of my lockdep anntotation patches
from a while ago:
https://lore.kernel.org/dri-devel/20200610194101.1668038-1-daniel.vetter@ffwll.ch/
That patch has been in -mm for a few days already, but it immediately hit
some issues with xfs.
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.
The unit test stuff was the major drag until I figured out how to make
this very easy with the locking selftests.
Comments, review, testing all very much welcome.
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
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-11-20 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 9:54 Daniel Vetter [this message]
2020-11-20 9:54 ` [PATCH 1/3] mm: Track mmu notifiers in fs_reclaim_acquire/release Daniel Vetter
2020-11-20 18:23 ` Jason Gunthorpe
2020-11-20 9:54 ` [PATCH 2/3] mm: Extract might_alloc() debug check Daniel Vetter
2020-11-20 17:19 ` Randy Dunlap
2020-11-20 17:31 ` Daniel Vetter
2020-11-20 18:07 ` Jason Gunthorpe
2020-11-24 14:34 ` Daniel Vetter
2020-11-24 15:27 ` Jason Gunthorpe
2020-11-20 9:54 ` [PATCH 3/3] locking/selftests: Add testcases for fs_reclaim Daniel Vetter
2020-11-20 12:31 ` Peter Zijlstra
2020-11-20 9:54 ` [PATCH] drm/ttm: don't set page->mapping Daniel Vetter
2020-11-20 10:04 ` Christian König
2020-11-20 10:05 ` Daniel Vetter
2020-11-20 10:08 ` Christian König
2020-11-20 15:01 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201120095445.1195585-1-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).