From: Ming Lei <ming.lei@redhat.com>
To: Cheyenne Wills <cheyenne.wills@gmail.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: BUG: NULL pointer dereferenced within __blk_rq_map_sg
Date: Tue, 11 Feb 2025 20:13:16 +0800 [thread overview]
Message-ID: <Z6s-3LndN-Gt5sZB@fedora> (raw)
In-Reply-To: <CAHpsFVeew-p9xB9DB52Pk_6mXfFxJbT8p14h5+YRTKabEfU3BQ@mail.gmail.com>
On Fri, Feb 07, 2025 at 07:09:39PM -0700, Cheyenne Wills wrote:
> While I was setting up to test with linux 6.14-rc1 (under Xen), I ran
> into a consistent NULL ptr dereference within __blk_rq_map_sg when
> booting the system.
>
> Using git bisect I was able to narrow down the "bad" commit to:
>
> block: add a dma mapping iterator (b7175e24d6acf79d9f3af9ce9d3d50de1fa748ec)
>
> Building a kernel with the parent commit
> (2caca8fc7aad9ea9a6ea3ed26ed146b1e5f06fab) using the same .config does
> not fail.
>
> Following is the console log showing the error as well as the Xen
> (libvirt) configuration for the guest that I'm using.
>
> Please let me know if there is any additional information that I can provide.
Can you test the following patch?
diff --git a/block/blk-merge.c b/block/blk-merge.c
index b55c52a42303..1eabde8383fb 100644
--- a/block/blk-merge.c
+++ b/block/blk-merge.c
@@ -493,7 +493,7 @@ static bool blk_map_iter_next(struct request *req,
return true;
}
- if (!iter->iter.bi_size)
+ if (!iter->bio || !iter->iter.bi_size)
return false;
bv = mp_bvec_iter_bvec(iter->bio->bi_io_vec, iter->iter);
@@ -514,7 +514,8 @@ static bool blk_map_iter_next(struct request *req,
if (!iter->bio->bi_next)
break;
iter->bio = iter->bio->bi_next;
- iter->iter = iter->bio->bi_iter;
+ if (iter->bio)
+ iter->iter = iter->bio->bi_iter;
}
next = mp_bvec_iter_bvec(iter->bio->bi_io_vec, iter->iter);
Thanks,
Ming
next prev parent reply other threads:[~2025-02-11 12:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 2:09 BUG: NULL pointer dereferenced within __blk_rq_map_sg Cheyenne Wills
2025-02-11 12:13 ` Ming Lei [this message]
2025-02-11 15:28 ` Ming Lei
2025-02-12 23:24 ` Cheyenne Wills
2025-02-13 1:29 ` Ming Lei
2025-02-13 6:32 ` Christoph Hellwig
2025-02-13 6:38 ` Christoph Hellwig
2025-02-13 12:39 ` Cheyenne Wills
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=Z6s-3LndN-Gt5sZB@fedora \
--to=ming.lei@redhat.com \
--cc=cheyenne.wills@gmail.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).