From: Vasily Gorbik <gor@linux.ibm.com>
To: syzbot <syzbot+09ddb593eea76a158f42@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] general protection fault in bio_alloc_bioset
Date: Sat, 21 Mar 2026 23:52:42 +0100 [thread overview]
Message-ID: <ttc9u7u@ub.hpns> (raw)
In-Reply-To: <69bdcdcd.050a0220.3bf4de.002f.GAE@google.com>
#syz test
diff --git a/block/bio.c b/block/bio.c
index 5057047194c4..77067fa346d3 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -581,11 +581,11 @@ struct bio *bio_alloc_bioset(struct block_device *bdev, unsigned short nr_vecs,
*/
opf &= ~REQ_ALLOC_CACHE;
- p = mempool_alloc(&bs->bio_pool, gfp);
+ p = mempool_alloc(&bs->bio_pool, saved_gfp);
bio = p + bs->front_pad;
if (nr_vecs > BIO_INLINE_VECS) {
nr_vecs = BIO_MAX_VECS;
- bvecs = mempool_alloc(&bs->bvec_pool, gfp);
+ bvecs = mempool_alloc(&bs->bvec_pool, saved_gfp);
}
}
--
2.53.0
next prev parent reply other threads:[~2026-03-21 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 22:44 [syzbot] [block?] general protection fault in bio_alloc_bioset syzbot
2026-03-21 6:09 ` Edward Adam Davis
2026-03-21 6:46 ` syzbot
2026-03-21 7:24 ` Edward Adam Davis
2026-03-21 7:55 ` syzbot
2026-03-21 8:36 ` [PATCH next] block: mempool alloc fail due to insufficient memory Edward Adam Davis
2026-03-21 14:17 ` Jens Axboe
2026-03-21 22:52 ` Vasily Gorbik [this message]
2026-03-22 0:18 ` [syzbot] [block?] general protection fault in bio_alloc_bioset syzbot
2026-03-22 2:23 ` Vasily Gorbik
2026-03-22 2:35 ` [PATCH] block: fix bio_alloc_bioset slowpath GFP handling Vasily Gorbik
2026-03-23 6:44 ` Christoph Hellwig
2026-03-23 13:58 ` Jens Axboe
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=ttc9u7u@ub.hpns \
--to=gor@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+09ddb593eea76a158f42@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