From: Eric Farman <farman@linux.ibm.com>
To: Farhan Ali <alifm@linux.ibm.com>, Cornelia Huck <cohuck@redhat.com>
Cc: pasic@linux.ibm.com, linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC v1 3/4] vfio-ccw: Set pa_nr to 0 if memory allocation fails for pa_iova_pfn
Date: Tue, 2 Jul 2019 12:24:28 -0400 [thread overview]
Message-ID: <7b7b1d6b-07b0-0fff-2a23-006ec67d7e3f@linux.ibm.com> (raw)
In-Reply-To: <96b27fc4-5899-b17e-0a93-31e7b69f80a7@linux.ibm.com>
On 7/2/19 10:07 AM, Farhan Ali wrote:
>
>
> On 07/02/2019 04:45 AM, Cornelia Huck wrote:
>> On Mon, 1 Jul 2019 12:23:45 -0400
>> Farhan Ali <alifm@linux.ibm.com> wrote:
>>
>>> So we clean up correctly.
You mean, "so we don't try to call vfio_unpin_pages()" ?
>>>
>>> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
>>> ---
>>> drivers/s390/cio/vfio_ccw_cp.c | 4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/s390/cio/vfio_ccw_cp.c
>>> b/drivers/s390/cio/vfio_ccw_cp.c
>>> index cab1be9..c5655de 100644
>>> --- a/drivers/s390/cio/vfio_ccw_cp.c
>>> +++ b/drivers/s390/cio/vfio_ccw_cp.c
>>> @@ -72,8 +72,10 @@ static int pfn_array_alloc(struct pfn_array *pa,
>>> u64 iova, unsigned int len)
>>> sizeof(*pa->pa_iova_pfn) +
>>> sizeof(*pa->pa_pfn),
>>> GFP_KERNEL);
>>> - if (unlikely(!pa->pa_iova_pfn))
>>> + if (unlikely(!pa->pa_iova_pfn)) {
>>> + pa->pa_nr = 0;
>>> return -ENOMEM;
>>> + }
>>> pa->pa_pfn = pa->pa_iova_pfn + pa->pa_nr;
>>> pa->pa_iova_pfn[0] = pa->pa_iova >> PAGE_SHIFT;
>>
>> This looks like an older error -- can you give a Fixes: tag? (Yeah, I
>> know I sound like a broken record wrt that tag... :)
>>
> Yes, this is an older error. And yup I will add a fixes tag :)
Seems okay.
Reviewed-by: Eric Farman <farman@linux.ibm.com>
next prev parent reply other threads:[~2019-07-02 16:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 16:23 [RFC v1 0/4] Some vfio-ccw fixes Farhan Ali
2019-07-01 16:23 ` [RFC v1 1/4] vfio-ccw: Set orb.cmd.c64 before calling ccwchain_handle_ccw Farhan Ali
2019-07-02 8:26 ` Cornelia Huck
2019-07-02 13:56 ` Farhan Ali
2019-07-02 15:11 ` Eric Farman
2019-07-03 9:30 ` Cornelia Huck
2019-07-08 13:34 ` Farhan Ali
2019-07-01 16:23 ` [RFC v1 2/4] vfio-ccw: No need to call cp_free on an error in cp_init Farhan Ali
2019-07-02 8:42 ` Cornelia Huck
2019-07-02 13:58 ` Farhan Ali
2019-07-02 16:15 ` Eric Farman
2019-07-02 16:48 ` Farhan Ali
2019-07-01 16:23 ` [RFC v1 3/4] vfio-ccw: Set pa_nr to 0 if memory allocation fails for pa_iova_pfn Farhan Ali
2019-07-02 8:45 ` Cornelia Huck
2019-07-02 14:07 ` Farhan Ali
2019-07-02 16:24 ` Eric Farman [this message]
2019-07-01 16:23 ` [RFC v1 4/4] vfio-ccw: Don't call cp_free if we are processing a channel program Farhan Ali
2019-07-02 9:51 ` Cornelia Huck
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=7b7b1d6b-07b0-0fff-2a23-006ec67d7e3f@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.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