* FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 5.4-stable tree
@ 2020-12-28 9:17 ` gregkh
2021-01-01 17:03 ` [PATCH 5.4 bp v2] ext4: don't remount read-only with errors=continue on reboot Jinoh Kang
0 siblings, 1 reply; 8+ messages in thread
From: gregkh @ 2020-12-28 9:17 UTC (permalink / raw)
To: jack, adilger, tytso; +Cc: stable
The patch below does not apply to the 5.4-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable@vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From b08070eca9e247f60ab39d79b2c25d274750441f Mon Sep 17 00:00:00 2001
From: Jan Kara <jack@suse.cz>
Date: Fri, 27 Nov 2020 12:33:54 +0100
Subject: [PATCH] ext4: don't remount read-only with errors=continue on reboot
ext4_handle_error() with errors=continue mount option can accidentally
remount the filesystem read-only when the system is rebooting. Fix that.
Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
Signed-off-by: Jan Kara <jack@suse.cz>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 872d45a131ca..3ef84e8ab1ae 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -666,19 +666,17 @@ static bool system_going_down(void)
static void ext4_handle_error(struct super_block *sb)
{
+ journal_t *journal = EXT4_SB(sb)->s_journal;
+
if (test_opt(sb, WARN_ON_ERROR))
WARN_ON_ONCE(1);
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
return;
- if (!test_opt(sb, ERRORS_CONT)) {
- journal_t *journal = EXT4_SB(sb)->s_journal;
-
- ext4_set_mount_flag(sb, EXT4_MF_FS_ABORTED);
- if (journal)
- jbd2_journal_abort(journal, -EIO);
- }
+ ext4_set_mount_flag(sb, EXT4_MF_FS_ABORTED);
+ if (journal)
+ jbd2_journal_abort(journal, -EIO);
/*
* We force ERRORS_RO behavior when system is rebooting. Otherwise we
* could panic during 'reboot -f' as the underlying device got already
^ permalink raw reply related [flat|nested] 8+ messages in thread
* FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 4.19-stable tree
@ 2020-12-28 9:17 gregkh
2021-01-01 14:58 ` [PATCH 5.4 bp] ext4: don't remount read-only with errors=continue on reboot Jinoh Kang
2021-01-01 15:09 ` [PATCH 4.19 bp] " Jinoh Kang
0 siblings, 2 replies; 8+ messages in thread
From: gregkh @ 2020-12-28 9:17 UTC (permalink / raw)
To: jack, adilger, tytso; +Cc: stable
The patch below does not apply to the 4.19-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to <stable@vger.kernel.org>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From b08070eca9e247f60ab39d79b2c25d274750441f Mon Sep 17 00:00:00 2001
From: Jan Kara <jack@suse.cz>
Date: Fri, 27 Nov 2020 12:33:54 +0100
Subject: [PATCH] ext4: don't remount read-only with errors=continue on reboot
ext4_handle_error() with errors=continue mount option can accidentally
remount the filesystem read-only when the system is rebooting. Fix that.
Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
Signed-off-by: Jan Kara <jack@suse.cz>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 872d45a131ca..3ef84e8ab1ae 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -666,19 +666,17 @@ static bool system_going_down(void)
static void ext4_handle_error(struct super_block *sb)
{
+ journal_t *journal = EXT4_SB(sb)->s_journal;
+
if (test_opt(sb, WARN_ON_ERROR))
WARN_ON_ONCE(1);
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
return;
- if (!test_opt(sb, ERRORS_CONT)) {
- journal_t *journal = EXT4_SB(sb)->s_journal;
-
- ext4_set_mount_flag(sb, EXT4_MF_FS_ABORTED);
- if (journal)
- jbd2_journal_abort(journal, -EIO);
- }
+ ext4_set_mount_flag(sb, EXT4_MF_FS_ABORTED);
+ if (journal)
+ jbd2_journal_abort(journal, -EIO);
/*
* We force ERRORS_RO behavior when system is rebooting. Otherwise we
* could panic during 'reboot -f' as the underlying device got already
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 5.4 bp] ext4: don't remount read-only with errors=continue on reboot
2020-12-28 9:17 FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 4.19-stable tree gregkh
@ 2021-01-01 14:58 ` Jinoh Kang
2020-12-28 9:17 ` FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 5.4-stable tree gregkh
2021-01-01 15:09 ` [PATCH 4.19 bp] " Jinoh Kang
1 sibling, 1 reply; 8+ messages in thread
From: Jinoh Kang @ 2021-01-01 14:58 UTC (permalink / raw)
To: Greg Kroah-Hartman; +Cc: Jan Kara, Andreas Dilger, Theodore Ts'o, stable
From: Jan Kara <jack@suse.cz>
commit b08070eca9e247f60ab39d79b2c25d274750441f upstream.
ext4_handle_error() with errors=continue mount option can accidentally
remount the filesystem read-only when the system is rebooting. Fix that.
Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
Signed-off-by: Jan Kara <jack@suse.cz>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
fs/ext4/super.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 920658ca8777..06568467b0c2 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -455,19 +455,17 @@ static bool system_going_down(void)
static void ext4_handle_error(struct super_block *sb)
{
+ journal_t *journal = EXT4_SB(sb)->s_journal;
+
if (test_opt(sb, WARN_ON_ERROR))
WARN_ON_ONCE(1);
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
return;
- if (!test_opt(sb, ERRORS_CONT)) {
- journal_t *journal = EXT4_SB(sb)->s_journal;
-
- EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
- if (journal)
- jbd2_journal_abort(journal, -EIO);
- }
+ EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
+ if (journal)
+ jbd2_journal_abort(journal, -EIO);
/*
* We force ERRORS_RO behavior when system is rebooting. Otherwise we
* could panic during 'reboot -f' as the underlying device got already
--
2.26.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 4.19 bp] ext4: don't remount read-only with errors=continue on reboot
2020-12-28 9:17 FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 4.19-stable tree gregkh
2021-01-01 14:58 ` [PATCH 5.4 bp] ext4: don't remount read-only with errors=continue on reboot Jinoh Kang
@ 2021-01-01 15:09 ` Jinoh Kang
2021-01-01 16:40 ` [PATCH 4.19 bp v2] " Jinoh Kang
1 sibling, 1 reply; 8+ messages in thread
From: Jinoh Kang @ 2021-01-01 15:09 UTC (permalink / raw)
To: Greg Kroah-Hartman; +Cc: Jan Kara, Andreas Dilger, Theodore Ts'o, stable
From: Jan Kara <jack@suse.cz>
commit b08070eca9e247f60ab39d79b2c25d274750441f upstream.
ext4_handle_error() with errors=continue mount option can accidentally
remount the filesystem read-only when the system is rebooting. Fix that.
Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
Signed-off-by: Jan Kara <jack@suse.cz>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
---
fs/ext4/super.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index ee96f504ed78..e9e9f09f5370 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -454,19 +454,17 @@ static bool system_going_down(void)
static void ext4_handle_error(struct super_block *sb)
{
+ journal_t *journal = EXT4_SB(sb)->s_journal;
+
if (test_opt(sb, WARN_ON_ERROR))
WARN_ON_ONCE(1);
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
return;
- if (!test_opt(sb, ERRORS_CONT)) {
- journal_t *journal = EXT4_SB(sb)->s_journal;
-
- EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
- if (journal)
- jbd2_journal_abort(journal, -EIO);
- }
+ EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
+ if (journal)
+ jbd2_journal_abort(journal, -EIO);
/*
* We force ERRORS_RO behavior when system is rebooting. Otherwise we
* could panic during 'reboot -f' as the underlying device got already
--
2.26.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 4.19 bp v2] ext4: don't remount read-only with errors=continue on reboot
2021-01-01 15:09 ` [PATCH 4.19 bp] " Jinoh Kang
@ 2021-01-01 16:40 ` Jinoh Kang
2021-01-04 10:35 ` Jan Kara
0 siblings, 1 reply; 8+ messages in thread
From: Jinoh Kang @ 2021-01-01 16:40 UTC (permalink / raw)
To: Greg Kroah-Hartman; +Cc: Jan Kara, Andreas Dilger, Theodore Ts'o, stable
From: Jan Kara <jack@suse.cz>
commit b08070eca9e247f60ab39d79b2c25d274750441f upstream.
ext4_handle_error() with errors=continue mount option can accidentally
remount the filesystem read-only when the system is rebooting. Fix that.
Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
Signed-off-by: Jan Kara <jack@suse.cz>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
[jinoh: backport accounting for missing
commit 9b5f6c9b83d9 ("ext4: make s_mount_flags modifications atomic")]
Signed-off-by: Jinoh Kang <jinoh.kang.kr@gmail.com>
---
v1 --> v2: added missing comment and signoff
Apologies for wasted traffic...
---
fs/ext4/super.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index ee96f504ed78..e9e9f09f5370 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -454,19 +454,17 @@ static bool system_going_down(void)
static void ext4_handle_error(struct super_block *sb)
{
+ journal_t *journal = EXT4_SB(sb)->s_journal;
+
if (test_opt(sb, WARN_ON_ERROR))
WARN_ON_ONCE(1);
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
return;
- if (!test_opt(sb, ERRORS_CONT)) {
- journal_t *journal = EXT4_SB(sb)->s_journal;
-
- EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
- if (journal)
- jbd2_journal_abort(journal, -EIO);
- }
+ EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
+ if (journal)
+ jbd2_journal_abort(journal, -EIO);
/*
* We force ERRORS_RO behavior when system is rebooting. Otherwise we
* could panic during 'reboot -f' as the underlying device got already
--
2.26.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [PATCH 5.4 bp v2] ext4: don't remount read-only with errors=continue on reboot
2020-12-28 9:17 ` FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 5.4-stable tree gregkh
@ 2021-01-01 17:03 ` Jinoh Kang
2021-01-04 10:35 ` Jan Kara
0 siblings, 1 reply; 8+ messages in thread
From: Jinoh Kang @ 2021-01-01 17:03 UTC (permalink / raw)
To: Greg Kroah-Hartman; +Cc: Jan Kara, Andreas Dilger, Theodore Ts'o, stable
From: Jan Kara <jack@suse.cz>
commit b08070eca9e247f60ab39d79b2c25d274750441f upstream.
ext4_handle_error() with errors=continue mount option can accidentally
remount the filesystem read-only when the system is rebooting. Fix that.
Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
Signed-off-by: Jan Kara <jack@suse.cz>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cc: stable@kernel.org
Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
[jinoh: backport accounting for missing
commit 9b5f6c9b83d9 ("ext4: make s_mount_flags modifications atomic")]
Signed-off-by: Jinoh Kang <jinoh.kang.kr@gmail.com>
---
v1 --> v2: added missing comment and signoff
Apologies for wasted traffic...
Please disregard the previous mail, which was in a wrong thread:
- <5611c936-5913-d570-36a4-2b2ed209cd88@gmail.com> [PATCH 5.4 bp]
That said, the patches for 4.19 and 5.4 have the same patch ID.
---
fs/ext4/super.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 920658ca8777..06568467b0c2 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -455,19 +455,17 @@ static bool system_going_down(void)
static void ext4_handle_error(struct super_block *sb)
{
+ journal_t *journal = EXT4_SB(sb)->s_journal;
+
if (test_opt(sb, WARN_ON_ERROR))
WARN_ON_ONCE(1);
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
return;
- if (!test_opt(sb, ERRORS_CONT)) {
- journal_t *journal = EXT4_SB(sb)->s_journal;
-
- EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
- if (journal)
- jbd2_journal_abort(journal, -EIO);
- }
+ EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
+ if (journal)
+ jbd2_journal_abort(journal, -EIO);
/*
* We force ERRORS_RO behavior when system is rebooting. Otherwise we
* could panic during 'reboot -f' as the underlying device got already
--
2.26.2
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH 5.4 bp v2] ext4: don't remount read-only with errors=continue on reboot
2021-01-01 17:03 ` [PATCH 5.4 bp v2] ext4: don't remount read-only with errors=continue on reboot Jinoh Kang
@ 2021-01-04 10:35 ` Jan Kara
0 siblings, 0 replies; 8+ messages in thread
From: Jan Kara @ 2021-01-04 10:35 UTC (permalink / raw)
To: Jinoh Kang
Cc: Greg Kroah-Hartman, Jan Kara, Andreas Dilger, Theodore Ts'o, stable
On Fri 01-01-21 17:03:21, Jinoh Kang wrote:
> From: Jan Kara <jack@suse.cz>
>
> commit b08070eca9e247f60ab39d79b2c25d274750441f upstream.
>
> ext4_handle_error() with errors=continue mount option can accidentally
> remount the filesystem read-only when the system is rebooting. Fix that.
>
> Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
> Signed-off-by: Jan Kara <jack@suse.cz>
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>
> Cc: stable@kernel.org
> Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> [jinoh: backport accounting for missing
> commit 9b5f6c9b83d9 ("ext4: make s_mount_flags modifications atomic")]
> Signed-off-by: Jinoh Kang <jinoh.kang.kr@gmail.com>
> ---
> v1 --> v2: added missing comment and signoff
> Apologies for wasted traffic...
>
> Please disregard the previous mail, which was in a wrong thread:
> - <5611c936-5913-d570-36a4-2b2ed209cd88@gmail.com> [PATCH 5.4 bp]
> That said, the patches for 4.19 and 5.4 have the same patch ID.
The backport looks good to me. Thanks!
Honza
> ---
> fs/ext4/super.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 920658ca8777..06568467b0c2 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -455,19 +455,17 @@ static bool system_going_down(void)
>
> static void ext4_handle_error(struct super_block *sb)
> {
> + journal_t *journal = EXT4_SB(sb)->s_journal;
> +
> if (test_opt(sb, WARN_ON_ERROR))
> WARN_ON_ONCE(1);
>
> - if (sb_rdonly(sb))
> + if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
> return;
>
> - if (!test_opt(sb, ERRORS_CONT)) {
> - journal_t *journal = EXT4_SB(sb)->s_journal;
> -
> - EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
> - if (journal)
> - jbd2_journal_abort(journal, -EIO);
> - }
> + EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
> + if (journal)
> + jbd2_journal_abort(journal, -EIO);
> /*
> * We force ERRORS_RO behavior when system is rebooting. Otherwise we
> * could panic during 'reboot -f' as the underlying device got already
> --
> 2.26.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH 4.19 bp v2] ext4: don't remount read-only with errors=continue on reboot
2021-01-01 16:40 ` [PATCH 4.19 bp v2] " Jinoh Kang
@ 2021-01-04 10:35 ` Jan Kara
0 siblings, 0 replies; 8+ messages in thread
From: Jan Kara @ 2021-01-04 10:35 UTC (permalink / raw)
To: Jinoh Kang
Cc: Greg Kroah-Hartman, Jan Kara, Andreas Dilger, Theodore Ts'o, stable
On Fri 01-01-21 16:40:58, Jinoh Kang wrote:
> From: Jan Kara <jack@suse.cz>
>
> commit b08070eca9e247f60ab39d79b2c25d274750441f upstream.
>
> ext4_handle_error() with errors=continue mount option can accidentally
> remount the filesystem read-only when the system is rebooting. Fix that.
>
> Fixes: 1dc1097ff60e ("ext4: avoid panic during forced reboot")
> Signed-off-by: Jan Kara <jack@suse.cz>
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>
> Cc: stable@kernel.org
> Link: https://lore.kernel.org/r/20201127113405.26867-2-jack@suse.cz
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> [jinoh: backport accounting for missing
> commit 9b5f6c9b83d9 ("ext4: make s_mount_flags modifications atomic")]
> Signed-off-by: Jinoh Kang <jinoh.kang.kr@gmail.com>
> ---
> v1 --> v2: added missing comment and signoff
> Apologies for wasted traffic...
The backport looks good to me.
Honza
> ---
> fs/ext4/super.c | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index ee96f504ed78..e9e9f09f5370 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -454,19 +454,17 @@ static bool system_going_down(void)
>
> static void ext4_handle_error(struct super_block *sb)
> {
> + journal_t *journal = EXT4_SB(sb)->s_journal;
> +
> if (test_opt(sb, WARN_ON_ERROR))
> WARN_ON_ONCE(1);
>
> - if (sb_rdonly(sb))
> + if (sb_rdonly(sb) || test_opt(sb, ERRORS_CONT))
> return;
>
> - if (!test_opt(sb, ERRORS_CONT)) {
> - journal_t *journal = EXT4_SB(sb)->s_journal;
> -
> - EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
> - if (journal)
> - jbd2_journal_abort(journal, -EIO);
> - }
> + EXT4_SB(sb)->s_mount_flags |= EXT4_MF_FS_ABORTED;
> + if (journal)
> + jbd2_journal_abort(journal, -EIO);
> /*
> * We force ERRORS_RO behavior when system is rebooting. Otherwise we
> * could panic during 'reboot -f' as the underlying device got already
> --
> 2.26.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2021-01-04 10:36 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-28 9:17 FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 4.19-stable tree gregkh
2021-01-01 14:58 ` [PATCH 5.4 bp] ext4: don't remount read-only with errors=continue on reboot Jinoh Kang
2020-12-28 9:17 ` FAILED: patch "[PATCH] ext4: don't remount read-only with errors=continue on reboot" failed to apply to 5.4-stable tree gregkh
2021-01-01 17:03 ` [PATCH 5.4 bp v2] ext4: don't remount read-only with errors=continue on reboot Jinoh Kang
2021-01-04 10:35 ` Jan Kara
2021-01-01 15:09 ` [PATCH 4.19 bp] " Jinoh Kang
2021-01-01 16:40 ` [PATCH 4.19 bp v2] " Jinoh Kang
2021-01-04 10:35 ` Jan Kara
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.