Re: [PATCH 0/5] Backport to 4.9- ext4: protect journal inode's blocks using block_validity

[Ashwin H <ashwinh@xxxxxxxxxx>]

I have sent patches for 4.14 tree

Thanks,
Ashwin

On 29/04/20, 6:29 PM, "Greg KH" <gregkh@xxxxxxxxxxxxxxxxxxx> 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