From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext4 bugfixes for 4.4
Date: Sun, 6 Dec 2015 22:40:55 -0500 [thread overview]
Message-ID: <20151207034055.GA424@thunk.org> (raw)
The following changes since commit be69e1c19f0efb091f29521715c380842fa4cd7e:
fs/ext4: remove unnecessary new_valid_dev check (2015-10-29 14:18:13 -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 087ffd4eae9929afd06f6a709861df3c3508492a:
jbd2: fix null committed data return in undo_access (2015-12-04 12:29:28 -0500)
----------------------------------------------------------------
Ext4 bug fixes for v4.4, including fixes for post-2038 time encodings,
some endian conversion problems with ext4 encryption, potential memory
leaks after truncate in data=journal mode, and an ocfs2 regression
caused by a jbd2 performance improvement.
----------------------------------------------------------------
Al Viro (2):
ext4: fix an endianness bug in ext4_encrypted_zeroout()
ext4: fix an endianness bug in ext4_encrypted_follow_link()
David Turner (1):
ext4: Fix handling of extended tv_sec
Jan Kara (1):
jbd2: Fix unreclaimed pages after truncate in data=journal mode
Junxiao Bi (1):
jbd2: fix null committed data return in undo_access
Xu Cang (1):
ext4: add "static" to ext4_seq_##name##_fops struct
fs/ext4/crypto.c | 2 +-
fs/ext4/ext4.h | 51 ++++++++++++++++++++++++++++++++++++++++++++-------
fs/ext4/symlink.c | 2 +-
fs/ext4/sysfs.c | 2 +-
fs/jbd2/transaction.c | 12 +++++++++---
5 files changed, 56 insertions(+), 13 deletions(-)
reply other threads:[~2015-12-07 3:40 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=20151207034055.GA424@thunk.org \
--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;
as well as URLs for NNTP newsgroup(s).