mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Edward Adam Davis <eadavis@qq.com>
To: syzbot+f6539d4ce3f775aee0cc@syzkaller.appspotmail.com
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] kernel BUG in bio_chain
Date: Mon,  8 Dec 2025 12:20:36 +0800	[thread overview]
Message-ID: <tencent_3DF47A826C5C2C056C8C96ACEBF6EDBACD0A@qq.com> (raw)
In-Reply-To: <69351d9c.a70a0220.38f243.0049.GAE@google.com>

#syz test

diff --git a/fs/gfs2/lops.c b/fs/gfs2/lops.c
index 97ebe457c00a..2de334034c74 100644
--- a/fs/gfs2/lops.c
+++ b/fs/gfs2/lops.c
@@ -484,6 +484,10 @@ static struct bio *gfs2_chain_bio(struct bio *prev, unsigned int nr_iovecs)
 	new = bio_alloc(prev->bi_bdev, nr_iovecs, prev->bi_opf, GFP_NOIO);
 	bio_clone_blkg_association(new, prev);
 	new->bi_iter.bi_sector = bio_end_sector(prev);
+	new->bi_end_io = prev->bi_end_io;
+	new->bi_private = prev->bi_private;
+	prev->bi_end_io = NULL;
+	prev->bi_private = NULL;
 	bio_chain(prev, new);
 	submit_bio(prev);
 	return new;


  reply	other threads:[~2025-12-08  4:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07  6:24 syzbot
2025-12-08  4:20 ` Edward Adam Davis [this message]
2025-12-08  6:10   ` syzbot
2025-12-08  6:12 ` [PATCH Next] gfs2: update end and prev bio for chain bio Edward Adam Davis
2025-12-12 12:47   ` Andreas Gruenbacher
2025-12-14  2:17     ` Edward Adam Davis
2026-01-14  8:46       ` Andreas Gruenbacher
2025-12-12 12:17 ` Forwarded: syzbot
     [not found] <CAHc6FU6EFYSMkK5Kz0mdikb+YJQg9Yga0-SfWNr0x-L-PaBzuw@mail.gmail.com>
2025-12-12 13:33 ` [syzbot] [block?] kernel BUG in bio_chain 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_3DF47A826C5C2C056C8C96ACEBF6EDBACD0A@qq.com \
    --to=eadavis@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+f6539d4ce3f775aee0cc@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

all inboxes | Powered by JetHome®