public inbox for linux-um@lists.infradead.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-um@lists.infradead.org,
	Richard Weinberger <richard@nod.at>,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>
Subject: [GIT PULL] uml-for-7.1-rc1
Date: Mon, 20 Apr 2026 15:26:12 +0200	[thread overview]
Message-ID: <20260420132821.364484-3-johannes@sipsolutions.net> (raw)

Hi Linus,

UML doesn't have a lot of content right now. However, I should
note that Michael Bommarito, who shows up here with a build fix,
has been doing a sort of (LLM-assisted) security audit, so we'll
likely be back after -rc1 with fixes.

Please pull and let us know if there's any problem.

Thanks,
johannes



The following changes since commit f338e77383789c0cae23ca3d48adcc5e9e137e3c:

  Linux 7.0-rc4 (2026-03-15 13:52:05 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/uml/linux.git tags/uml-for-7.1-rc1

for you to fetch changes up to 6522fe5c1b007c376fc5f2de1016c99a18b0af8e:

  um: Disable GCOV_PROFILE_ALL on 32-bit UML with Clang 20/21 (2026-04-10 09:28:59 +0200)

----------------------------------------------------------------
Mostly cleanups and small things, notably:
 - musl libc compatibility
 - vDSO installation fix
 - TLB sync race fix for recent SMP support
 - build fix for 32-bit with Clang 20/21

----------------------------------------------------------------
Kees Cook (2):
      um: Replace strncpy() with strnlen()+memcpy_and_pad() in strncpy_chunk_from_user()
      um: Disable GCOV_PROFILE_ALL on 32-bit UML with Clang 20/21

Marcel W. Wysocki (2):
      um: fix address-of CMSG_DATA() rvalue in stub
      um: avoid struct sigcontext redefinition with musl

Michael Bommarito (1):
      um: drivers: call kernel_strrchr() explicitly in cow_user.c

Randy Dunlap (1):
      um: time-travel: clean up kernel-doc warnings

Thomas Weißschuh (1):
      x86/um: fix vDSO installation

Tiwei Bie (3):
      um: Fix potential race condition in TLB sync
      um: Fix pte_read() and pte_exec() for kernel mappings
      um: Remove CONFIG_FRAME_WARN from x86_64_defconfig

 arch/um/Kconfig                    | 4 +++-
 arch/um/configs/x86_64_defconfig   | 1 -
 arch/um/drivers/cow_user.c         | 8 +++++++-
 arch/um/include/asm/pgtable.h      | 9 ++++-----
 arch/um/kernel/skas/stub.c         | 2 +-
 arch/um/kernel/skas/uaccess.c      | 4 ++--
 arch/um/kernel/tlb.c               | 4 ++--
 arch/x86/Makefile.um               | 2 ++
 arch/x86/um/os-Linux/mcontext.c    | 6 ++++++
 arch/x86/um/vdso/Makefile          | 2 --
 include/uapi/linux/um_timetravel.h | 6 +++++-
 mm/Kconfig                         | 1 +
 12 files changed, 33 insertions(+), 16 deletions(-)


             reply	other threads:[~2026-04-20 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-20 13:26 Johannes Berg [this message]
2026-04-21  0:31 ` [GIT PULL] uml-for-7.1-rc1 pr-tracker-bot

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=20260420132821.364484-3-johannes@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.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