From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: GIT PULL] ext4 fixes for 5.10-rc2
Date: Thu, 29 Oct 2020 00:24:55 -0400 [thread overview]
Message-ID: <20201029042455.GA1241260@mit.edu> (raw)
The following changes since commit 96485e4462604744d66bf4301557d996d80b85eb:
Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2020-10-22 10:31:08 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_fixes
for you to fetch changes up to 6694875ef8045cdb1e6712ee9b68fe08763507d8:
ext4: indicate that fast_commit is available via /sys/fs/ext4/feature/... (2020-10-28 13:43:22 -0400)
----------------------------------------------------------------
Bug fixes for the new ext4 fast commit feature, plus a fix for the
data=journal bug fix. Also use the generic casefolding support which
has now landed in fs/libfs.c for 5.10.
----------------------------------------------------------------
Andrea Righi (1):
ext4: properly check for dirty state in ext4_inode_datasync_dirty()
Daniel Rosenberg (1):
ext4: use generic casefolding support
Harshad Shirwadkar (4):
ext4: fix double locking in ext4_fc_commit_dentry_updates()
ext4: make num of fast commit blocks configurable
ext4: use s_mount_flags instead of s_mount_state for fast commit state
ext4: use IS_ERR() for error checking of path
Jan Kara (1):
ext4: fix mmap write protection for data=journal mode
Mauro Carvalho Chehab (1):
jbd2: fix a kernel-doc markup
Theodore Ts'o (1):
ext4: indicate that fast_commit is available via /sys/fs/ext4/feature/...
yangerkun (1):
ext4: do not use extent after put_bh
fs/ext4/dir.c | 64 ++--------------------------------------------------------------
fs/ext4/ext4.h | 20 ++++----------------
fs/ext4/extents.c | 30 +++++++++++++++---------------
fs/ext4/fast_commit.c | 37 ++++++++++++++++++++++++-------------
fs/ext4/hash.c | 2 +-
fs/ext4/inode.c | 15 +++++++++------
fs/ext4/namei.c | 20 ++++++++------------
fs/ext4/super.c | 16 ++++++++--------
fs/ext4/sysfs.c | 2 ++
include/linux/jbd2.h | 7 +++++--
10 files changed, 78 insertions(+), 135 deletions(-)
reply other threads:[~2020-10-29 7:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201029042455.GA1241260@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.