[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1587713792.git.ashwinh@vmware.com>
Date: Thu, 30 Apr 2020 00:51:34 +0530
From: ashwin-h <ashwinh@...are.com>
To: <tytso@....edu>, <adilger.kernel@...ger.ca>
CC: <linux-ext4@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<stable@...nel.org>, <srivatsab@...are.com>,
<srivatsa@...il.mit.edu>, <rostedt@...dmis.org>,
<srostedt@...are.com>, <gregkh@...uxfoundation.org>,
<ashwin.hiranniah@...il.com>, ashwin-h <ashwinh@...are.com>
Subject: [PATCH 0/5] Backport to 4.9- ext4: protect journal inode's blocks using block_validity
[PATCH 1/5] ext4: avoid declaring fs inconsistent due to invalid file
handles
This patch is backported as functionality in this commit is used by
Patch 2 in this patchset.
[PATCH 2/5] ext4: protect journal inode's blocks using block_validity
Backport to 4.9
[PATCH 3/5] ext4: don't perform block validity checks on the journal
[PATCH 4/5] ext4: fix block validity checks for journal inodes using
[PATCH 5/5] ext4: unsigned int compared against zero
Fixes issues found in Patch 2 in this patchset.
These patches addresses CVE-2019-19319
Colin Ian King (1):
ext4: unsigned int compared against zero
Theodore Ts'o (4):
ext4: avoid declaring fs inconsistent due to invalid file handles
ext4: protect journal inode's blocks using block_validity
ext4: don't perform block validity checks on the journal inode
ext4: fix block validity checks for journal inodes using indirect
blocks
fs/ext4/block_validity.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++
fs/ext4/ext4.h | 15 ++++++++++++--
fs/ext4/extents.c | 12 +++++++----
fs/ext4/ialloc.c | 2 +-
fs/ext4/inode.c | 48 ++++++++++++++++++++++++++++++------------
fs/ext4/ioctl.c | 2 +-
fs/ext4/namei.c | 4 ++--
fs/ext4/resize.c | 5 +++--
fs/ext4/super.c | 19 +++++------------
9 files changed, 122 insertions(+), 39 deletions(-)
--
2.7.4
Powered by blists - more mailing lists