From: Jens Axboe <axboe@kernel.dk>
To: jglisse@redhat.com, linux-kernel@vger.kernel.org
Cc: linux-block@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] block: do not leak memory in bio_copy_user_iov()
Date: Wed, 10 Apr 2019 16:14:52 -0600 [thread overview]
Message-ID: <e25d90b2-62ff-18bc-efe2-ef37c56bfa52@kernel.dk> (raw)
In-Reply-To: <20190410202751.20712-1-jglisse@redhat.com>
On 4/10/19 2:27 PM, jglisse@redhat.com wrote:
> From: Jérôme Glisse <jglisse@redhat.com>
>
> When bio_add_pc_page() fails in bio_copy_user_iov() we should free
> the page we just allocated otherwise we are leaking it.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2019-04-10 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 20:27 jglisse
2019-04-10 22:13 ` Chaitanya Kulkarni
2019-04-10 22:14 ` Jens Axboe [this message]
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=e25d90b2-62ff-18bc-efe2-ef37c56bfa52@kernel.dk \
--to=axboe@kernel.dk \
--cc=jglisse@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®