public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
	Linux Kernel Developers List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] ext4 updates for v6.9
Date: Wed, 13 Mar 2024 23:56:09 -0400	[thread overview]
Message-ID: <20240314035609.GA856050@mit.edu> (raw)

The following changes since commit 54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478:

  Linux 6.8-rc3 (2024-02-04 12:20:36 +0000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus-6.9-rc1

for you to fetch changes up to 0ecae5410ab526225293d2591ca4632b22c2fd8c:

  ext4: initialize sbi->s_freeclusters_counter and sbi->s_dirtyclusters_counter before use in kunit test (2024-03-07 13:32:54 -0500)

----------------------------------------------------------------
Ext4 bug fixes and cleanups for 6.9-rc1, plus some additional kunit
tests.

----------------------------------------------------------------
Arnd Bergmann (1):
      ext4: kunit: use dynamic inode allocation

Baokun Li (1):
      ext4: correct best extent lstart adjustment logic

Cheng Nie (1):
      ext4: fix the comment of ext4_map_blocks()/ext4_ext_map_blocks()

Chengming Zhou (1):
      ext4: remove SLAB_MEM_SPREAD flag usage

Jan Kara (4):
      ext4: fold quota accounting into ext4_xattr_inode_lookup_create()
      ext4: drop duplicate ea_inode handling in ext4_xattr_block_set()
      ext4: don't report EOPNOTSUPP errors from discard
      ext4: verify s_clusters_per_group even without bigalloc

Kemeng Shi (8):
      ext4: Add unit test for test_free_blocks_simple
      ext4: Add unit test of ext4_mb_generate_buddy
      ext4: Add unit test for mb_mark_used
      ext4: Add unit test for mb_free_blocks
      ext4: Add unit test for ext4_mb_mark_diskspace_used
      ext4: alloc test super block from sget
      ext4: hold group lock in ext4 kunit test
      ext4: initialize sbi->s_freeclusters_counter and sbi->s_dirtyclusters_counter before use in kunit test

Maximilian Heyne (1):
      ext4: fix corruption during on-line resize

Srivathsa Dara (1):
      ext4: enable meta_bg only when new desc blocks are needed

Wenchao Hao (1):
      ext4: remove unused parameter biop in ext4_issue_discard()

Ye Bin (1):
      ext4: forbid commit inconsistent quota data when errors=remount-ro

Zhang Yi (1):
      ext4: add a hint for block bitmap corrupt state in mb_groups

yangerkun (2):
      ext4: remove unused buddy_loaded in ext4_mb_seq_groups_show
      ext4: improve error msg for ext4_mb_seq_groups_show

 fs/ext4/extents.c      |   6 +-
 fs/ext4/inode.c        |  10 +-
 fs/ext4/mballoc-test.c | 601 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
 fs/ext4/mballoc.c      |  62 +++---
 fs/ext4/resize.c       |   5 +-
 fs/ext4/super.c        |  45 +++--
 fs/ext4/xattr.c        |  61 +++---
 7 files changed, 680 insertions(+), 110 deletions(-)

             reply	other threads:[~2024-03-14  3:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  3:56 Theodore Ts'o [this message]
2024-03-15 17:20 ` [GIT PULL] ext4 updates for v6.9 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=20240314035609.GA856050@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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