From: syzbot <syzbot+3db654d91b471c4d7a7d@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] debug: log uptodate states for iomap bug
Date: Mon, 21 Sep 2026 11:03:55 -0700 [thread overview]
Message-ID: <6ab1718b.a6af0033.177e91.0018.GAE@google.com> (raw)
In-Reply-To: <6aab8055.71f81b7d.278072.0016.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] debug: log uptodate states for iomap bug
Author: nsvatoslav515@gmail.com
Signed-off-by: Svyatoslav Nikolenko <nsvatoslav515@gmail.com>
---
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 238650ef6c7c
fs/iomap/buffered-io.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
index 0a5ebfda90f1..37596bae664d 100644
--- a/fs/iomap/buffered-io.c
+++ b/fs/iomap/buffered-io.c
@@ -291,8 +291,13 @@ static void ifs_free(struct folio *folio)
return;
WARN_ON_ONCE(ifs->read_bytes_pending != 0);
WARN_ON_ONCE(atomic_read(&ifs->write_bytes_pending));
- WARN_ON_ONCE(ifs_is_fully_uptodate(folio, ifs) !=
- folio_test_uptodate(folio));
+
+ bool ifs_up = ifs_is_fully_uptodate(folio, ifs);
+ bool folio_up = folio_test_uptodate(folio);
+
+ if (WARN_ON_ONCE(ifs_up != folio_up))
+ pr_err("IOMAP DEBUG: ifs_up=%d, folio_up=%d\n", ifs_up, folio_up);
+
kfree(ifs);
}
--
2.47.3
prev parent reply other threads:[~2026-09-21 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 5:53 [syzbot] [ntfs3?] WARNING in ntfs_evict_inode syzbot
2026-09-20 9:11 ` Forwarded: " syzbot
2026-09-20 9:28 ` syzbot
2026-09-20 10:34 ` syzbot
2026-09-20 11:01 ` syzbot
2026-09-20 12:52 ` syzbot
2026-09-21 14:04 ` syzbot
2026-09-21 14:28 ` Forwarded: [PATCH] debug: log uptodate states for iomap bug syzbot
2026-09-21 17:24 ` [PATCH] ntfs3: sync uptodate with iomap folio state in read_folio Adarsh Das
2026-09-21 18:03 ` syzbot [this message]
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=6ab1718b.a6af0033.177e91.0018.GAE@google.com \
--to=syzbot+3db654d91b471c4d7a7d@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®