From: Pavel Skripkin <paskripkin@gmail.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca, johann@whamcloud.com
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Pavel Skripkin <paskripkin@gmail.com>,
syzbot+c9ff4822a62eee994ea3@syzkaller.appspotmail.com
Subject: [PATCH] ext4: avoid huge mmp update interval value
Date: Thu, 5 Aug 2021 18:14:18 +0300 [thread overview]
Message-ID: <20210805151418.30659-1-paskripkin@gmail.com> (raw)
Syzbot reported task hung bug in ext4_fill_super(). The problem was in
too huge mmp update interval.
Syzkaller reproducer setted s_mmp_update_interval to 39785 seconds. This
update interaval is unreasonable huge and it can cause tasks to hung on
kthread_stop() call, since it will wait until timeout timer expires.
To avoid this sutiation, I've added MIN and MAX constants for kmmp
interval and clamped s_mmp_update_interval within the boundaries
Reported-and-tested-by: syzbot+c9ff4822a62eee994ea3@syzkaller.appspotmail.com
Fixes: c5e06d101aaf ("ext4: add support for multiple mount protection")
Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
---
Hi, Ted and ext4 maintainers!
I am not sure about min/max values for interval, so I look forward to
receiving your views on these values and patch in general!
With regards,
Pavel Skripkin
---
fs/ext4/mmp.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/fs/ext4/mmp.c b/fs/ext4/mmp.c
index bc364c119af6..160abee66dce 100644
--- a/fs/ext4/mmp.c
+++ b/fs/ext4/mmp.c
@@ -7,6 +7,9 @@
#include "ext4.h"
+#define EXT4_KMMP_MAX_INTERVAL 100
+#define EXT4_KMMP_MIN_INTERVAL 5
+
/* Checksumming functions */
static __le32 ext4_mmp_csum(struct super_block *sb, struct mmp_struct *mmp)
{
@@ -140,6 +143,12 @@ static int kmmpd(void *data)
unsigned long diff;
int retval;
+ /* We should avoid unreasonable huge update interval, since it can cause
+ * task hung bug on umount or on error handling path in ext4_fill_super()
+ */
+ mmp_update_interval = clamp(mmp_update_interval, EXT4_KMMP_MIN_INTERVAL,
+ EXT4_KMMP_MAX_INTERVAL);
+
mmp_block = le64_to_cpu(es->s_mmp_block);
mmp = (struct mmp_struct *)(bh->b_data);
mmp->mmp_time = cpu_to_le64(ktime_get_real_seconds());
@@ -156,6 +165,9 @@ static int kmmpd(void *data)
memcpy(mmp->mmp_nodename, init_utsname()->nodename,
sizeof(mmp->mmp_nodename));
+ ext4_msg(sb, KERN_INFO, "Started kmmp thread with update interval = %u\n",
+ mmp_update_interval);
+
while (!kthread_should_stop() && !sb_rdonly(sb)) {
if (!ext4_has_feature_mmp(sb)) {
ext4_warning(sb, "kmmpd being stopped since MMP feature"
--
2.32.0
next reply other threads:[~2021-08-05 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 15:14 Pavel Skripkin [this message]
2021-08-05 19:45 ` [PATCH] ext4: avoid huge mmp update interval value Theodore Ts'o
2021-08-05 20:12 ` Pavel Skripkin
2021-08-05 22:59 ` Dave Chinner
2021-08-06 10:20 ` Pavel Skripkin
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=20210805151418.30659-1-paskripkin@gmail.com \
--to=paskripkin@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=johann@whamcloud.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+c9ff4822a62eee994ea3@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox