From: Theodore Ts'o <tytso@mit.edu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-ext4@vger.kernel.org
Subject: [GIT PULL] ext4 bug fixes for 3.7
Date: Mon, 22 Oct 2012 18:19:59 -0400 [thread overview]
Message-ID: <20121022221959.GA16531@thunk.org> (raw)
The following changes since commit c278531d39f3158bfee93dc67da0b77e09776de2:
ext4: fix ext4_flush_completed_IO wait semantics (2012-10-05 11:31:55 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git tags/ext4_for_linus
for you to fetch changes up to 5de35e8d5c02d271c20e18337e01bc20e6ef472e:
ext4: Avoid underflow in ext4_trim_fs() (2012-10-22 18:01:19 -0400)
----------------------------------------------------------------
Various bug fixes for ext4. The most serious of them fixes a security
bug (CVE-2012-4508) which leads to stale data exposure when we have
fallocate racing against writes to files undergoing delayed
allocation. We also have two fixes for the metadata checksum feature,
the most serious of which can cause the superblock to have a invalid
checksum after a power failure.
----------------------------------------------------------------
Dmitry Monakhov (2):
ext4: serialize fallocate with ext4_convert_unwritten_extents
ext4: race-condition protection for ext4_convert_unwritten_extents_endio
Lukas Czerner (2):
ext4: fix undefined bit shift result in ext4_fill_flex_info
ext4: Avoid underflow in ext4_trim_fs()
Tao Ma (1):
ext4: Checksum the block bitmap properly with bigalloc enabled
Theodore Ts'o (1):
ext4: fix metadata checksum calculation for the superblock
fs/ext4/balloc.c | 8 +++----
fs/ext4/bitmap.c | 6 ++++--
fs/ext4/ext4.h | 7 +++----
fs/ext4/ext4_jbd2.c | 8 ++-----
fs/ext4/extents.c | 60 +++++++++++++++++++++++++++++++++++++++++++----------
fs/ext4/ialloc.c | 4 +---
fs/ext4/mballoc.c | 14 ++++++-------
fs/ext4/resize.c | 3 +--
fs/ext4/super.c | 9 ++++----
9 files changed, 74 insertions(+), 45 deletions(-)
reply other threads:[~2012-10-22 22:20 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=20121022221959.GA16531@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@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).