linux-kernel - Re: [PATCH] staging: erofs: keep corrupted fs from crashing kernel in erofs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <429f1337-76e4-cc2a-63e0-62a091f1dcf4@huawei.com>
Date:   Wed, 30 Jan 2019 23:28:10 +0800
From:   Gao Xiang <gaoxiang25@...wei.com>
To:     Sasha Levin <sashal@...nel.org>
CC:     Chao Yu <yuchao0@...wei.com>, Al Viro <viro@...IV.linux.org.uk>,
        LKML <linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>
Subject: Re: [PATCH] staging: erofs: keep corrupted fs from crashing kernel in
 erofs_namei()

Hi Sasha,

I will send v4.19 patch independently to the stable mailing list
after It gets carefully reviewed by Chao (and Al Viro if it is possible...)

Thanks,
Gao Xiang

On 2019/1/30 22:46, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: d72d1ce60174 staging: erofs: add namei functions.
> 
> The bot has tested the following trees: v4.20.5, v4.19.18.
> 
> v4.20.5: Build OK!
> v4.19.18: Failed to apply! Possible dependencies:
>     6e78901a9f23 ("staging: erofs: separate erofs_get_meta_page")
>     7dd68b147d60 ("staging: erofs: use explicit unsigned int type")
>     8be31270362b ("staging: erofs: introduce erofs_grab_bio")
>     ab47dd2b0819 ("staging: erofs: cleanup z_erofs_vle_work_{lookup, register}")
> 
> 
> How should we proceed with this patch?
> 
> --
> Thanks,
> Sasha
>