On 2022-08-17 20:29, Thomas Deutschmann wrote:
I will do another round with 2b7196a219bf (good) <-> 5.18 (bad).
...and this one also ended up in
first bad commit: [fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf] Linux 5.16-rc1
Now I built vanilla 5.18.18 and fsfreeze will hang after FIFREEZE ioctl
system call after running my reproducer which generated I/O load.
=> So looks like bug is still present, right?
When I now just edit Makefile and set KV <5.16-rc1, i.e.
diff --git a/Makefile b/Makefile
index 23162e2bdf14..0f344944d828 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
-PATCHLEVEL = 18
-SUBLEVEL = 18
+PATCHLEVEL = 15
+SUBLEVEL = 0
EXTRAVERSION =
NAME = Superb Owl
then I can no longer reproduce the problem.
Of course,
diff --git a/Makefile b/Makefile
index 23162e2bdf14..0f344944d828 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
-PATCHLEVEL = 18
-SUBLEVEL = 18
+PATCHLEVEL = 15
+SUBLEVEL = 99
EXTRAVERSION =
NAME = Superb Owl
will freeze again.
For me it looks like kernel is taking a different code path depending on
KV but I don't know how to proceed. Any idea how to continue debugging this?
--
Regards,
Thomas
