From: Harsh Shandilya <harsh@prjkt.io>
To: stable@vger.kernel.org
Cc: Harsh Shandilya <harsh@prjkt.io>
Subject: [PATCH 0/3] 4.17-rc1 stable tagged ext4 patches for 3.18.y
Date: Sat, 21 Apr 2018 17:51:45 +0530 [thread overview]
Message-ID: <20180421122145.19137-1-harsh@prjkt.io> (raw)
In-Reply-To: <20180420222612.18881-1-harsh@prjkt.io>
I've dropped one of the initial 4 patches since it required
a dependency patch that was ~250 lines in size and not really
suitable for -stable.
Theodore Ts'o (3):
ext4: add validity checks for bitmap block numbers
ext4: fail ext4_iget for root directory if unallocated
ext4: don't allow r/w mounts if metadata blocks overlap the superblock
fs/ext4/balloc.c | 16 ++++++++++++++--
fs/ext4/ialloc.c | 8 +++++++-
fs/ext4/inode.c | 6 ++++++
fs/ext4/super.c | 6 ++++++
4 files changed, 33 insertions(+), 3 deletions(-)
--
2.15.0.2308.g658a28aa74af
prev parent reply other threads:[~2018-04-21 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 22:26 [PATCH 0/4] 4.17-rc1 stable tagged ext4 patches for 3.18.y Harsh Shandilya
2018-04-20 22:26 ` [PATCH 1/4] ext4: add validity checks for bitmap block numbers Harsh Shandilya
2018-04-21 12:28 ` [PATCH 1/3] " Harsh Shandilya
2018-04-20 22:26 ` [PATCH 2/4] ext4: fail ext4_iget for root directory if unallocated Harsh Shandilya
2018-04-21 12:28 ` [PATCH 2/3] " Harsh Shandilya
2018-04-20 22:26 ` [PATCH 3/4] ext4: don't allow r/w mounts if metadata blocks overlap the superblock Harsh Shandilya
2018-04-21 12:29 ` [PATCH 3/3] " Harsh Shandilya
2018-04-21 20:07 ` Theodore Y. Ts'o
2018-04-22 2:30 ` Harsh Shandilya
2018-04-22 4:01 ` Theodore Y. Ts'o
2018-04-22 4:04 ` Harsh Shandilya
2018-04-20 22:26 ` [PATCH 4/4] ext4: force revalidation of directory pointer after seekdir(2) Harsh Shandilya
2018-04-20 23:23 ` [PATCH 0/4] 4.17-rc1 stable tagged ext4 patches for 3.18.y Harsh Shandilya
2018-04-21 12:21 ` Harsh Shandilya [this message]
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=20180421122145.19137-1-harsh@prjkt.io \
--to=harsh@prjkt.io \
--cc=stable@vger.kernel.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.