From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org,
George Zhang <georgezhang@vmware.com>,
Andy king <acking@vmware.com>, Dmitry Torokhov <dtor@vmware.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/1] Fix: vmw_vmci driver get_user_pages_fast error handling
Date: Thu, 2 Nov 2017 18:46:12 +0000 [thread overview]
Message-ID: <20171102184612.GL21978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20171031230038.7476-1-mathieu.desnoyers@efficios.com>
On Tue, Oct 31, 2017 at 07:00:38PM -0400, Mathieu Desnoyers wrote:
> Comparing a signed return value against an unsigned num_pages
> field performs the comparison as "unsigned", and therefore mistakenly
> considers get_user_pages_fast() errors as success.
It's worse than that - if you look into the code in question you'll
see
pr_debug("get_user_pages_fast(produce) failed (retval=%d)",
retval);
qp_release_pages(produce_q->kernel_if->u.h.header_page,
retval, false);
err = VMCI_ERROR_NO_MEM;
goto out;
with
static void qp_release_pages(struct page **pages,
u64 num_pages, bool dirty)
{
int i;
for (i = 0; i < num_pages; i++) {
if (dirty)
set_page_dirty(pages[i]);
put_page(pages[i]);
pages[i] = NULL;
}
}
Now, guess what'll happen if you get there with retval being negative?
AFAICS, the right fix is something along the lines of
if (retval != produce_q->kernel_if->num_pages) {
pr_debug("get_user_pages_fast(produce) failed (retval=%d)",
retval);
if (retval > 0)
qp_release_pages(produce_q->kernel_if->u.h.header_page,
retval, false);
err = VMCI_ERROR_NO_MEM;
goto out;
}
and similar for the second caller. Objections?
next prev parent reply other threads:[~2017-11-02 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 23:00 [PATCH 1/1] Fix: vmw_vmci driver get_user_pages_fast error handling Mathieu Desnoyers
2017-11-02 18:46 ` Al Viro [this message]
2017-11-02 18:54 ` Mathieu Desnoyers
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=20171102184612.GL21978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=acking@vmware.com \
--cc=dtor@vmware.com \
--cc=georgezhang@vmware.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.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;
as well as URLs for NNTP newsgroup(s).