From: Edward Adam Davis <eadavis@qq.com>
To: syzbot+1659aaaaa8d9d11265d7@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] INFO: task hung in filename_unlinkat
Date: Fri, 6 Mar 2026 09:18:23 +0800 [thread overview]
Message-ID: <tencent_7C8CAC27C106F792D846454989EEFD2EE906@qq.com> (raw)
In-Reply-To: <699ebd11.a00a0220.21906d.0005.GAE@google.com>
#syz test
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index ae3804f36535..4779da94f816 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -4457,9 +4457,13 @@ int ext4_ext_map_blocks(handle_t *handle, struct inode *inode,
path = ext4_ext_insert_extent(handle, inode, path, &newex, flags);
if (IS_ERR(path)) {
err = PTR_ERR(path);
- if (allocated_clusters) {
+ /*
+ * Gracefully handle out of space conditions. If the filesystem
+ * is inconsistent, we'll just leak allocated blocks to avoid
+ * causing even more damage.
+ */
+ if (allocated_clusters && (err == -EDQUOT || err == -ENOSPC)) {
int fb_flags = 0;
-
/*
* free data blocks we just allocated.
* not a good idea to call discard here directly,
next prev parent reply other threads:[~2026-03-06 1:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 9:12 syzbot
2026-03-01 8:32 ` Edward Adam Davis
2026-03-01 8:57 ` syzbot
2026-03-01 10:12 ` [PATCH] ext4: avoid infinite loops caused by data conflicts Edward Adam Davis
2026-03-02 10:52 ` [syzbot ci] " syzbot ci
2026-03-02 12:51 ` [PATCH v2] " Edward Adam Davis
2026-03-03 7:47 ` [syzbot ci] " syzbot ci
2026-03-02 13:01 ` [PATCH] " Jan Kara
2026-03-05 7:25 ` [PATCH v3] ext4: avoid infinite loops caused by residual data Edward Adam Davis
2026-03-05 10:38 ` Jan Kara
2026-03-05 12:10 ` Edward Adam Davis
2026-03-05 14:12 ` [PATCH v4] " Edward Adam Davis
2026-03-05 15:41 ` Jan Kara
2026-03-06 1:31 ` [PATCH v5] " Edward Adam Davis
2026-03-06 15:25 ` Jan Kara
2026-03-27 4:06 ` Theodore Ts'o
2026-03-05 4:51 ` [syzbot] [ext4?] INFO: task hung in filename_unlinkat Edward Adam Davis
2026-03-05 5:20 ` syzbot
2026-03-05 6:33 ` Edward Adam Davis
2026-03-05 6:56 ` syzbot
2026-03-05 12:20 ` Edward Adam Davis
2026-03-05 13:59 ` syzbot
2026-03-06 1:18 ` Edward Adam Davis [this message]
2026-03-06 2:07 ` syzbot
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=tencent_7C8CAC27C106F792D846454989EEFD2EE906@qq.com \
--to=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1659aaaaa8d9d11265d7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome