linux-kernel - Re: [PATCH 4.19 07/29] ext4: dont remount read-only with errors=continue on reboot

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 for Android: free password hash cracker in your pocket

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

Message-ID: <X/b7eY6izK+MIht+@kroah.com>
Date:   Thu, 7 Jan 2021 13:15:53 +0100
From:   "greg@...ah.com" <greg@...ah.com>
To:     Partha Nayak <partha.nayak@...anix.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4.19 07/29] ext4: dont remount read-only with
 errors=continue on reboot

On Thu, Jan 07, 2021 at 11:39:14AM +0000, Partha Nayak wrote:
> Hi Greg / Linux community
> 
> I was going through the patch details: https://www.spinics.net/lists/stable/msg436529.html .
> 
> In our case the superblock for EXT4 is configured to trigger a kernel panic . But inspite of that the file system was mounted as read-only . We are on 4.19.12 .

4.19.12 is _VERY_ old and obsolete and totally insecure and is not
supported by the community, it was released over two years ago.

Why not apply the patch you link here and see if it solves your issue?

Or, better yet, move to 4.19.165, or 5.10.y?  What prevents you from
doing that?

good luck!

greg k-h