All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashwin H <ashwinh@vmware.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "tytso@mit.edu" <tytso@mit.edu>,
	"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>,
	Srivatsa Bhat <srivatsab@vmware.com>,
	"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	Steven Rostedt <srostedt@vmware.com>,
	"ashwin.hiranniah@gmail.com" <ashwin.hiranniah@gmail.com>
Subject: Re: [PATCH 0/5] Backport to 4.9- ext4: protect journal inode's blocks using block_validity
Date: Wed, 29 Apr 2020 20:39:45 +0000	[thread overview]
Message-ID: <A37B50A5-C978-47A6-9861-048AEA9788EE@vmware.com> (raw)
In-Reply-To: <20200429125909.GA2124190@kroah.com>

I have sent patches for 4.14 tree

Thanks,
Ashwin

On 29/04/20, 6:29 PM, "Greg KH" <gregkh@linuxfoundation.org> wrote:

    On Thu, Apr 30, 2020 at 12:51:34AM +0530, ashwin-h wrote:
    > [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
    
    I can't take patches for 4.9 that are not also in 4.14, for the obvious
    reason that you never want to upgrade to a newer kernel and get
    regressions.
    
    So can you provide a backported series for the 4.14 tree too?  Then I
    can take these.
    
    thanks,
    
    greg k-h
    


  reply	other threads:[~2020-04-29 20:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 19:21 [PATCH 0/5] Backport to 4.9- ext4: protect journal inode's blocks using block_validity ashwin-h
2020-04-29 12:59 ` Greg KH
2020-04-29 20:39   ` Ashwin H [this message]
2020-05-01 12:10     ` Greg KH
2020-04-29 19:21 ` [PATCH 1/5] ext4: avoid declaring fs inconsistent due to invalid file handles ashwin-h
2020-04-29 19:21 ` [PATCH 2/5] ext4: protect journal inode's blocks using block_validity ashwin-h
2020-04-29 19:21 ` [PATCH 3/5] ext4: don't perform block validity checks on the journal inode ashwin-h
2020-04-29 19:21 ` [PATCH 4/5] ext4: fix block validity checks for journal inodes using indirect blocks ashwin-h
2020-04-29 19:21 ` [PATCH 5/5] ext4: unsigned int compared against zero ashwin-h

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=A37B50A5-C978-47A6-9861-048AEA9788EE@vmware.com \
    --to=ashwinh@vmware.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=ashwin.hiranniah@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=srivatsa@csail.mit.edu \
    --cc=srivatsab@vmware.com \
    --cc=srostedt@vmware.com \
    --cc=stable@kernel.org \
    --cc=tytso@mit.edu \
    /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.