From: "Theodore Ts'o" <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 fixes for 5.1-rc1
Date: Sun, 19 May 2019 01:58:48 -0400 [thread overview]
Message-ID: <20190519055848.GA16693@mit.edu> (raw)
The following changes since commit db90f41916cf04c020062f8d8b0385942248283e:
ext4: export /sys/fs/ext4/feature/casefold if Unicode support is present (2019-05-06 14:03:52 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus_stable
for you to fetch changes up to 2c1d0e3631e5732dba98ef49ac0bec1388776793:
ext4: avoid panic during forced reboot due to aborted journal (2019-05-17 17:37:18 -0400)
----------------------------------------------------------------
Some bug fixes, and an update to the URL's for the final version of
Unicode 12.1.0.
----------------------------------------------------------------
Chengguang Xu (1):
jbd2: fix potential double free
Colin Ian King (1):
ext4: unsigned int compared against zero
Jan Kara (1):
ext4: avoid panic during forced reboot due to aborted journal
Lukas Czerner (1):
ext4: fix data corruption caused by overlapping unaligned and aligned IO
Sahitya Tummala (1):
ext4: fix use-after-free in dx_release()
Sriram Rajagopalan (1):
ext4: zero out the unused memory region in the extent tree block
Theodore Ts'o (4):
ext4: fix miscellaneous sparse warnings
unicode: add missing check for an error return from utf8lookup()
unicode: update to Unicode 12.1.0 final
ext4: fix block validity checks for journal inodes using indirect blocks
fs/ext4/block_validity.c | 8 +++++++-
fs/ext4/extents.c | 17 +++++++++++++++--
fs/ext4/file.c | 7 +++++++
fs/ext4/fsmap.c | 2 +-
fs/ext4/ioctl.c | 2 +-
fs/ext4/namei.c | 5 ++++-
fs/ext4/super.c | 4 ++--
fs/jbd2/journal.c | 49 +++++++++++++++++++++++++++++++------------------
fs/jbd2/revoke.c | 32 ++++++++++++++++++++------------
fs/jbd2/transaction.c | 8 +++++---
fs/unicode/README.utf8data | 28 +++++++---------------------
fs/unicode/utf8-norm.c | 2 ++
include/linux/jbd2.h | 8 +++++---
13 files changed, 107 insertions(+), 65 deletions(-)
next reply other threads:[~2019-05-19 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 5:58 Theodore Ts'o [this message]
2019-05-19 19:10 ` [GIT PULL] ext4 fixes for 5.1-rc1 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=20190519055848.GA16693@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.