Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition

To: "968567@bugs.debian.org" <968567@bugs.debian.org>
Subject: Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
From: "Craig, Daniel (CASS, Marsfield)" <Daniel.Craig@csiro.au>
Date: Thu, 10 Sep 2020 04:47:20 +0000
Message-id: <[🔎] SY3PR01MB162870D72A7C38FD69B2B498FF270@SY3PR01MB1628.ausprd01.prod.outlook.com>
Reply-to: "Craig, Daniel (CASS, Marsfield)" <Daniel.Craig@csiro.au>, 968567@bugs.debian.org
References: <159768435221.35277.6894327133461351597.reportbug@ertok>

Hi,

I can confirm the existence of this CPU soft-lock bug with gfs2.

I won't worry about reproducing the kernel bug message, but I have done a bit of digging and if I revert the following commit, added in the 4.19.130 release then this fixes issue for me.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=c91cffd0fd010c06d67f3a9a528b858ce28c60fb

Note that the problem is still present in the latest upstream release in the 4.19 series (4.19.144)

I've reported this bug in the kernel bugzilla, referenced here:

https://bugzilla.kernel.org/show_bug.cgi?id=209217

Cheers,

Daniel Craig

Reply to:

Follow-Ups:
- Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
  - From: Salvatore Bonaccorso <carnil@debian.org>

Prev by Date: Processed: closing 941597
Next by Date: Bug#970011: linux: missing build dependency on kernel-wedge in stage1 build
Previous by thread: Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
Next by thread: Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
Index(es):
- Date
- Thread