From: Dmitry Antipov <dmantipov@yandex.ru>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
lvc-project@linuxtesting.org, netdev@vger.kernel.org
Subject: Re: [PATCH 6.12] block: fix memory leak in in bio_map_user_iov()
Date: Fri, 08 May 2026 11:30:05 +0300 [thread overview]
Message-ID: <5bd98789901e6bcd2b41d646209deb6e48ffb711.camel@yandex.ru> (raw)
In-Reply-To: <20260507212200-2614841ccc112a082cab6938-pchelkin@ispras>
On Thu, 2026-05-07 at 21:52 +0300, Fedor Pchelkin wrote:
> In some form the issue is present in current upstream as well. For
> example, there is another callsite of iov_iter_extract_pages() in
> block/bio-integrity.c where the same pattern still persists.
Good point, and skb_splice_from_iter() looks suspicious as well:
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
index 7dad68e3b518..bf053372acb2 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -7343,12 +7343,16 @@ ssize_t skb_splice_from_iter(struct sk_buff *skb, struct iov_iter *iter,
len = iov_iter_extract_pages(iter, &ppages, maxsize, nr, 0, &off);
if (len <= 0) {
+ /* Possible memory leak - ppages should be vfree()'d
+ if reallocated (ppages != pages)? */
ret = len ?: -EIO;
break;
}
i = 0;
do {
+ /* This looks wrong if reallocated - ppages[i++]
+ should be used instead? */
struct page *page = pages[i++];
size_t part = min_t(size_t, PAGE_SIZE - off, len);
This issue likely crosses the boundaries of block subsystem so netdev
people are encouraged to look as well.
Dmitry
next parent reply other threads:[~2026-05-08 8:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260505094529.406783-1-dmantipov@yandex.ru>
[not found] ` <20260507212200-2614841ccc112a082cab6938-pchelkin@ispras>
2026-05-08 8:30 ` Dmitry Antipov [this message]
2026-05-08 11:16 ` [PATCH 6.12] block: fix memory leak in in bio_map_user_iov() Fedor Pchelkin
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=5bd98789901e6bcd2b41d646209deb6e48ffb711.camel@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pchelkin@ispras.ru \
--cc=stable@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