public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Linux 6.4.3
Date: Tue, 11 Jul 2023 06:53:59 +0200	[thread overview]
Message-ID: <2023071100-studied-state-715a@gregkh> (raw)

I'm announcing the release of the 6.4.3 kernel.

All users of the 6.4 kernel series must upgrade.

The updated 6.4.y git tree can be found at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.4.y
and can be browsed at the normal kernel.org git web browser:
	https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary

thanks,

greg k-h

------------

 Makefile                     |    2 +-
 include/linux/bootmem_info.h |    2 ++
 kernel/fork.c                |    1 +
 mm/memory.c                  |    7 +++++++
 mm/mmap.c                    |    6 ++++++
 5 files changed, 17 insertions(+), 1 deletion(-)

Greg Kroah-Hartman (1):
      Linux 6.4.3

Hugh Dickins (1):
      mm: lock newly mapped VMA with corrected ordering

Liu Shixin (1):
      bootmem: remove the vmemmap pages from kmemleak in free_bootmem_page

Peter Collingbourne (1):
      mm: call arch_swap_restore() from do_swap_page()

Suren Baghdasaryan (3):
      mm: lock a vma before stack expansion
      mm: lock newly mapped VMA which can be modified after it becomes visible
      fork: lock VMAs of the parent process when forking


             reply	other threads:[~2023-07-11  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  4:53 Greg Kroah-Hartman [this message]
2023-07-11  4:54 ` Linux 6.4.3 Greg Kroah-Hartman

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=2023071100-studied-state-715a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@vger.kernel.org \
    --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