Thread (19 messages) 19 messages, 6 authors, 2024-08-21

Re: [PATCH v2 1/4] mm: Add optional close() to struct vm_special_mapping

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: 2024-08-19 20:16:08
Also in: linux-mm, linux-sh, linux-um, lkml

On Mon, 19 Aug 2024 at 12:51, Nathan Chancellor [off-list ref] wrote:
Yes, that appears to fix it for me. I don't have much to say about the
rest but others might :)
Ok, I did a quick hack-job to remove that disgusting
install_special_mapping() legacy case.

With this, the old "install_special_mapping()" mess no longer exists,
but I haven't even attempted to compile the result, because I don't
have cross-compile environments for any of the affected architectures.

Except UML. I did at least build it there, but it's not like I tested it.

Adding architecture maintainers and more architecture lists to the
participants. It would be good to actually get this patch tested.
Context for newly added people:

   https://lore.kernel.org/all/CAHk-=wj9QPhG4CjiX8YLRC1wHj_Qs-T8wJi0WEhkfp0cszvB9w@mail.gmail.com/ (local)

NOTE! This patch is against my current tree, not the linux-next
changes. But it should entirely remove the case that caused problems
in linux-next.

                      Linus
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help