All of lore.kernel.org
 help / color / mirror / Atom feed
From: "greg@kroah.com" <greg@kroah.com>
To: Partha Nayak <partha.nayak@nutanix.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4.19 07/29] ext4: dont remount read-only with errors=continue on reboot
Date: Thu, 7 Jan 2021 13:15:53 +0100	[thread overview]
Message-ID: <X/b7eY6izK+MIht+@kroah.com> (raw)
In-Reply-To: <BYAPR02MB4759ADB966DDEAAE42B11EAA88AF0@BYAPR02MB4759.namprd02.prod.outlook.com>

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

       reply	other threads:[~2021-01-07 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR02MB4759194730E06BCDC10892AC88AF0@BYAPR02MB4759.namprd02.prod.outlook.com>
     [not found] ` <BYAPR02MB4759ADB966DDEAAE42B11EAA88AF0@BYAPR02MB4759.namprd02.prod.outlook.com>
2021-01-07 12:15   ` greg [this message]
2021-01-05  9:28 [PATCH 4.19 00/29] 4.19.165-rc2 review Greg Kroah-Hartman
2021-01-05  9:28 ` [PATCH 4.19 07/29] ext4: dont remount read-only with errors=continue on reboot Greg Kroah-Hartman

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=X/b7eY6izK+MIht+@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=partha.nayak@nutanix.com \
    /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.