mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 bugfixes for 4.8
Date: Mon, 29 Aug 2016 14:57:46 -0400	[thread overview]
Message-ID: <20160829185746.gbdh6pbfigcvbtyx@thunk.org> (raw)

The following changes since commit 7bc9491645118c9461bd21099c31755ff6783593:

  ext4: verify extent header depth (2016-07-15 00:22:07 -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 2e81a4eeedcaa66e35f58b81e0755b87057ce392:

  ext4: avoid deadlock when expanding inode size (2016-08-11 12:38:55 -0400)

----------------------------------------------------------------
Fix bugs that could cause kernel deadlocks or file system corruption
while moving xattrs to expand the extended inode.  Also add some
sanity checks to the block group descriptors to make sure we don't end
up overwriting the superblock.

----------------------------------------------------------------
Jan Kara (4):
      ext4: fix xattr shifting when expanding inodes
      ext4: fix xattr shifting when expanding inodes part 2
      ext4: properly align shifted xattrs when expanding inodes
      ext4: avoid deadlock when expanding inode size

Theodore Ts'o (2):
      ext4: reserve xattr index for the Hurd
      ext4: validate that metadata blocks do not overlap superblock

 fs/ext4/inode.c |  2 --
 fs/ext4/super.c | 18 +++++++++++++++++-
 fs/ext4/xattr.c | 53 +++++++++++++++++++++++++++++++----------------------
 fs/ext4/xattr.h |  1 +
 4 files changed, 49 insertions(+), 25 deletions(-)

                 reply	other threads:[~2016-08-29 18:57 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=20160829185746.gbdh6pbfigcvbtyx@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

all inboxes | Powered by JetHome®