Linux kernel -stable discussions
 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.16.3
Date: Sat, 23 Aug 2025 16:51:26 +0200	[thread overview]
Message-ID: <2025082354-halogen-retaliate-a8ba@gregkh> (raw)

I'm announcing the release of the 6.16.3 kernel.

All users of the 6.16 kernel series that use the ext4 filesystem should
upgrade.

The updated 6.16.y git tree can be found at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-6.16.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 
 fs/ext4/ext4.h              |    2 
 fs/ext4/extents.c           |    6 
 fs/ext4/inline.c            |    6 
 fs/ext4/inode.c             |  323 +++++++++++++++++++++++++++-----------------
 fs/ext4/move_extent.c       |    3 
 fs/ext4/xattr.c             |    2 
 include/trace/events/ext4.h |   47 +++++-
 8 files changed, 250 insertions(+), 141 deletions(-)

Greg Kroah-Hartman (1):
      Linux 6.16.3

Zhang Yi (9):
      ext4: process folios writeback in bytes
      ext4: move the calculation of wbc->nr_to_write to mpage_folio_done()
      ext4: fix stale data if it bail out of the extents mapping loop
      ext4: refactor the block allocation process of ext4_page_mkwrite()
      ext4: restart handle if credits are insufficient during allocating blocks
      ext4: enhance tracepoints during the folios writeback
      ext4: correct the reserved credits for extent conversion
      ext4: reserved credits for one extent during the folio writeback
      ext4: replace ext4_writepage_trans_blocks()


             reply	other threads:[~2025-08-23 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23 14:51 Greg Kroah-Hartman [this message]
2025-08-23 14:51 ` Linux 6.16.3 Greg Kroah-Hartman
2025-08-24 18:31 ` [REGRESSION] - BROKEN NETWORKING " Kyle Sanderson
2025-08-24 18:55   ` Willy Tarreau
2025-08-24 19:29     ` Calvin Owens
2025-08-24 19:51       ` Kyle Sanderson
2025-08-25  7:00   ` Greg Kroah-Hartman
2025-08-25  7:29     ` Greg Kroah-Hartman
2025-08-25  7:30       ` 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=2025082354-halogen-retaliate-a8ba@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