mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* linux-next: manual merge of the uml tree with the mm tree
@ 2026-09-25 11:54 Mark Brown
  2026-09-25 12:25 ` Lorenzo Stoakes (ARM)
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Brown @ 2026-09-25 11:54 UTC (permalink / raw)
  To: Richard Weinberger
  Cc: Andrew Morton, David Hildenbrand, Hajime Tazaki, Johannes Berg,
	Linux Kernel Mailing List, Linux Next Mailing List,
	Lorenzo Stoakes, Mike Rapoport, Ricardo Koller, Vlastimil Babka

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

Hi all,

Today's linux-next merge of the uml tree got a conflict in:

  arch/um/Kconfig

between commit:

  f56266a653013 ("mm: make userland page table freeing RCU-safe")

from the mm tree and commit:

  626ff2b34dbb7 ("um: allow deselecting CONFIG_MMU")

from the uml tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

diff --cc arch/um/Kconfig
index 94b8ff70f578b,59d62c74fc41f..0000000000000
--- a/arch/um/Kconfig
+++ b/arch/um/Kconfig
@@@ -44,10 -45,16 +45,15 @@@ config UM
  	select HAVE_SYSCALL_TRACEPOINTS
  	select THREAD_INFO_IN_TASK
  	select SPARSE_IRQ
 -	select MMU_GATHER_RCU_TABLE_FREE if MMU
+ 	select UACCESS_MEMCPY if !MMU
+ 	select GENERIC_STRNLEN_USER if !MMU
+ 	select GENERIC_STRNCPY_FROM_USER if !MMU
  
  config MMU
- 	bool
+ 	bool "MMU support"
  	default y
+ 	help
+ 	  Turning this off allows a nommu build, say Y.
  
  config UML_DMA_EMULATION
  	bool

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: linux-next: manual merge of the uml tree with the mm tree
  2026-09-25 11:54 linux-next: manual merge of the uml tree with the mm tree Mark Brown
@ 2026-09-25 12:25 ` Lorenzo Stoakes (ARM)
  0 siblings, 0 replies; 3+ messages in thread
From: Lorenzo Stoakes (ARM) @ 2026-09-25 12:25 UTC (permalink / raw)
  To: Mark Brown
  Cc: Richard Weinberger, Andrew Morton, David Hildenbrand,
	Hajime Tazaki, Johannes Berg, Linux Kernel Mailing List,
	Linux Next Mailing List, Mike Rapoport, Ricardo Koller,
	Vlastimil Babka

On Fri, Sep 25, 2026 at 12:54:35PM +0100, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the uml tree got a conflict in:
>
>   arch/um/Kconfig
>
> between commit:
>
>   f56266a653013 ("mm: make userland page table freeing RCU-safe")
>
> from the mm tree and commit:
>
>   626ff2b34dbb7 ("um: allow deselecting CONFIG_MMU")

Oh nice, nommu UML coming then :)

>
> from the uml tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> diff --cc arch/um/Kconfig
> index 94b8ff70f578b,59d62c74fc41f..0000000000000
> --- a/arch/um/Kconfig
> +++ b/arch/um/Kconfig
> @@@ -44,10 -45,16 +45,15 @@@ config UM
>   	select HAVE_SYSCALL_TRACEPOINTS
>   	select THREAD_INFO_IN_TASK
>   	select SPARSE_IRQ
>  -	select MMU_GATHER_RCU_TABLE_FREE if MMU
> + 	select UACCESS_MEMCPY if !MMU
> + 	select GENERIC_STRNLEN_USER if !MMU
> + 	select GENERIC_STRNCPY_FROM_USER if !MMU
>
>   config MMU
> - 	bool
> + 	bool "MMU support"
>   	default y
> + 	help
> + 	  Turning this off allows a nommu build, say Y.
>
>   config UML_DMA_EMULATION
>   	bool

LGTM thanks!

--
Cheers, Lorenzo

^ permalink raw reply	[flat|nested] 3+ messages in thread

* linux-next: manual merge of the uml tree with the mm tree
@ 2024-04-30 23:19 Stephen Rothwell
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2024-04-30 23:19 UTC (permalink / raw)
  To: Richard Weinberger, Andrew Morton
  Cc: Kent Overstreet, Linux Kernel Mailing List,
	Linux Next Mailing List, Suren Baghdasaryan, Tiwei Bie

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

Hi all,

Today's linux-next merge of the uml tree got a conflict in:

  arch/um/include/shared/um_malloc.h

between commit:

  88ae5fb755b0 ("mm: vmalloc: enable memory allocation profiling")

from the mm-unstable branch of the mm tree and commit:

  0c2b208c8b79 ("um: Fix the declaration of vfree")

from the uml tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc arch/um/include/shared/um_malloc.h
index bf503658f08e,d25084447c69..000000000000
--- a/arch/um/include/shared/um_malloc.h
+++ b/arch/um/include/shared/um_malloc.h
@@@ -11,9 -11,8 +11,9 @@@
  extern void *uml_kmalloc(int size, int flags);
  extern void kfree(const void *ptr);
  
 -extern void *vmalloc(unsigned long size);
 +extern void *vmalloc_noprof(unsigned long size);
 +#define vmalloc(...)		vmalloc_noprof(__VA_ARGS__)
- extern void vfree(void *ptr);
+ extern void vfree(const void *ptr);
  
  #endif /* __UM_MALLOC_H__ */
  

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-09-25 12:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-25 11:54 linux-next: manual merge of the uml tree with the mm tree Mark Brown
2026-09-25 12:25 ` Lorenzo Stoakes (ARM)
  -- strict thread matches above, loose matches on Subject: below --
2024-04-30 23:19 Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®