From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext4 fixes for 6.3-rc2
Date: Sat, 11 Mar 2023 23:41:16 -0500 [thread overview]
Message-ID: <20230312044116.GA2694785@mit.edu> (raw)
The following changes since commit e3645d72f8865ffe36f9dc811540d40aa3c848d3:
ext4: fix incorrect options show of original mount_opt and extend mount_opt2 (2023-02-25 15:39:08 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable
for you to fetch changes up to f5361da1e60d54ec81346aee8e3d8baf1be0b762:
ext4: zero i_disksize when initializing the bootloader inode (2023-03-11 00:44:24 -0500)
----------------------------------------------------------------
Bug fixes and regressions for ext4, the most serious of which is a
potential deadlock during directory renames that was introduced during
the merge window discovered by a combination of syzbot and lockdep.
----------------------------------------------------------------
Darrick J. Wong (1):
ext4: fix another off-by-one fsmap error on 1k block filesystems
Eric Biggers (1):
ext4: fix cgroup writeback accounting with fs-layer encryption
Eric Whitney (1):
ext4: fix RENAME_WHITEOUT handling for inline directories
Jan Kara (1):
ext4: Fix deadlock during directory rename
Theodore Ts'o (1):
ext4, jbd2: add an optimized bmap for the journal inode
Thomas Weißschuh (1):
ext4: make kobj_type structures constant
Tudor Ambarus (1):
ext4: Fix comment about the 64BIT feature
Wu Bo (1):
docs: ext4: modify the group desc size to 64
Ye Bin (4):
ext4: move where set the MAY_INLINE_DATA flag is set
ext4: fix WARNING in ext4_update_inline_data
ext4: commit super block if fs record error when journal record without error
ext4: make sure fs error flag setted before clear journal error
Zhihao Cheng (1):
ext4: zero i_disksize when initializing the bootloader inode
Documentation/filesystems/ext4/blockgroup.rst | 6 +++---
fs/ext4/ext4.h | 2 +-
fs/ext4/fsmap.c | 2 ++
fs/ext4/inline.c | 1 -
fs/ext4/inode.c | 7 +++++-
fs/ext4/ioctl.c | 1 +
fs/ext4/namei.c | 39 +++++++++++++++++++++-------------
fs/ext4/page-io.c | 11 +++++-----
fs/ext4/super.c | 38 +++++++++++++++++++++++++++++++--
fs/ext4/sysfs.c | 4 ++--
fs/ext4/xattr.c | 3 +++
fs/jbd2/journal.c | 9 +++++---
include/linux/jbd2.h | 8 +++++++
13 files changed, 98 insertions(+), 33 deletions(-)
next reply other threads:[~2023-03-12 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 4:41 Theodore Ts'o [this message]
2023-03-12 16:20 ` [GIT PULL] ext4 fixes for 6.3-rc2 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=20230312044116.GA2694785@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