From: "Theodore Ts'o" <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] ext4 bug fixes for 3.16
Date: Sun, 13 Jul 2014 16:10:18 -0400 [thread overview]
Message-ID: <20140713201018.GA31590@thunk.org> (raw)
The following changes since commit 16874b2cb867d3eb63ed838f2847143e11556708:
Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2014-06-29 19:20:43 -0700)
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 bf40c92635d63fcc574c52649f7cda13e0418ac1:
ext4: fix potential null pointer dereference in ext4_free_inode (2014-07-12 16:11:42 -0400)
----------------------------------------------------------------
More bug fixes for ext4 -- most importantly, a fix for a bug
(introduced in 3.15) that can end up triggering a file system
corruption error after a journal replay. (It shouldn't lead to any
actual data corruption, but it is scary and can force file systems to
be remounted read-only, etc.)
----------------------------------------------------------------
Eric Sandeen (1):
ext4: disable synchronous transaction batching if max_batch_time==0
Namjae Jeon (1):
ext4: fix potential null pointer dereference in ext4_free_inode
Theodore Ts'o (5):
ext4: fix unjournalled bg descriptor while initializing inode bitmap
ext4: clarify error count warning messages
ext4: clarify ext4_error message in ext4_mb_generate_buddy_error()
ext4: revert commit which was causing fs corruption after journal replays
ext4: fix a potential deadlock in __ext4_es_shrink()
fs/ext4/extents_status.c | 4 ++--
fs/ext4/ialloc.c | 16 ++++++++--------
fs/ext4/mballoc.c | 4 ++--
fs/ext4/super.c | 60 ++++++++++++++++++++++++++++--------------------------------
fs/jbd2/transaction.c | 5 ++++-
5 files changed, 44 insertions(+), 45 deletions(-)
next reply other threads:[~2014-07-13 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 20:10 Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-30 0:11 Theodore Ts'o
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=20140713201018.GA31590@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
Powered by JetHome