Skip to contentSkip to conversation

highmem-specify-that-kmap_local_page-is-callable-from-interrupts.patch removed from -mm tree

merged mm-stable Andrew Morton 1 participant 1 message Aug 9, 2022

lore
Share & tools
lore

Andrew Morton

author tree notice Applied
#0 lore raw

The quilt patch titled
Subject: highmem: specify that kmap_local_page() is callable from interrupts
has been removed from the -mm tree. Its filename was
highmem-specify-that-kmap_local_page-is-callable-from-interrupts.patch

This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: "Fabio M. De Francesco" <[email protected]>
Subject: highmem: specify that kmap_local_page() is callable from interrupts
Date: Thu, 28 Jul 2022 17:48:39 +0200

In a recent thread about converting kmap() to kmap_local_page(), the safety of calling kmap_local_page() was questioned.[1]

"any context" should probably be enough detail for users who want to know whether or not kmap_local_page() can be called from interrupts. However, Linux still has kmap_atomic() which might make users think they must use the latter in interrupts.

Add "including interrupts" for better clarity.

[1] https://lore.kernel.org/lkml/3187836.aeNJFYEL58@opensuse/

Cc Matthew Wilcox (Oracle) <[email protected]>
Cc Mike Rapoport <[email protected]>
Cc Sebastian Andrzej Siewior <[email protected]>
Cc Thomas Gleixner <[email protected]>
Cc Catalin Marinas <[email protected]>
Cc Jonathan Corbet <[email protected]>
Cc Peter Collingbourne <[email protected]>
Cc Vlastimil Babka <[email protected]>
Cc Will Deacon <[email protected]>

---

 include/linux/highmem.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/highmem.h renamed from include/linux/highmem.h~highmem-specify-that-kmap_local_page-is-callable-from-interrupts +1 -1
@@ -64,7 +64,7 @@ static inline void kmap_flush_unused(voi
  *
  * Returns: The virtual address of the mapping
  *
- * Can be invoked from any context.
+ * Can be invoked from any context, including interrupts.
  *
  * Requires careful handling when nesting multiple mappings because the map
  * management is stack based. The unmap has to be in the reverse order of

_

Patches currently in -mm which might be from [email protected] are