mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+085adc3f91549d11066a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] WARNING in can_finish_ordered_extent
Date: Fri, 02 Oct 2026 07:49:10 -0700	[thread overview]
Message-ID: <6abfc466.7503fbd6.2d3f6.001e.GAE@google.com> (raw)
In-Reply-To: <6a396a65.52ae72c2.136ac7.0001.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] WARNING in can_finish_ordered_extent
Author: adarshdas950@gmail.com

#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index d7600e5fa3d9..2117b2a80edd 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -1895,9 +1895,14 @@ static int submit_one_sector(struct btrfs_inode *inode,
 	queued = submit_extent_folio(bio_ctrl, disk_bytenr, folio,
 				     sectorsize, filepos - folio_pos(folio), 0);
 	if (unlikely(queued < sectorsize)) {
+		u32 unqueued = sectorsize - queued;
+
 		btrfs_folio_clear_writeback(fs_info, folio, filepos, sectorsize);
-		btrfs_mark_ordered_io_finished(inode, filepos, fs_info->sectorsize,
-					       false);
+		if (unqueued)
+			btrfs_mark_ordered_io_finished(inode, filepos + queued,
+						       unqueued, false);
+		if (bio_ctrl->bbio && bio_ctrl->bbio->bio.bi_iter.bi_size)
+			submit_one_bio(bio_ctrl);
 		return -EUCLEAN;
 	}
 	return 0;

  reply	other threads:[~2026-10-02 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 17:01 [syzbot] [btrfs?] " syzbot
2026-10-02 14:49 ` syzbot [this message]
2026-10-02 15:24 ` Forwarded: Re: [syzbot] " 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=6abfc466.7503fbd6.2d3f6.001e.GAE@google.com \
    --to=syzbot+085adc3f91549d11066a@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®