From: Cornelia Huck <cohuck@redhat.com>
To: Farhan Ali <alifm@linux.ibm.com>
Cc: farman@linux.ibm.com, pasic@linux.ibm.com,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [RFC v1 1/4] vfio-ccw: Set orb.cmd.c64 before calling ccwchain_handle_ccw
Date: Tue, 2 Jul 2019 10:26:06 +0200 [thread overview]
Message-ID: <20190702102606.2e9cfed3.cohuck@redhat.com> (raw)
In-Reply-To: <050943a6f5a427317ea64100bc2b4ec6394a4411.1561997809.git.alifm@linux.ibm.com>
On Mon, 1 Jul 2019 12:23:43 -0400
Farhan Ali <alifm@linux.ibm.com> wrote:
> Because ccwchain_handle_ccw calls ccwchain_calc_length and
> as per the comment we should set orb.cmd.c64 before calling
> ccwchanin_calc_length.
>
> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
> ---
> drivers/s390/cio/vfio_ccw_cp.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/s390/cio/vfio_ccw_cp.c b/drivers/s390/cio/vfio_ccw_cp.c
> index d6a8dff..5ac4c1e 100644
> --- a/drivers/s390/cio/vfio_ccw_cp.c
> +++ b/drivers/s390/cio/vfio_ccw_cp.c
> @@ -640,16 +640,16 @@ int cp_init(struct channel_program *cp, struct device *mdev, union orb *orb)
> memcpy(&cp->orb, orb, sizeof(*orb));
> cp->mdev = mdev;
>
> - /* Build a ccwchain for the first CCW segment */
> - ret = ccwchain_handle_ccw(orb->cmd.cpa, cp);
> - if (ret)
> - cp_free(cp);
> -
> /* It is safe to force: if not set but idals used
> * ccwchain_calc_length returns an error.
> */
> cp->orb.cmd.c64 = 1;
>
> + /* Build a ccwchain for the first CCW segment */
> + ret = ccwchain_handle_ccw(orb->cmd.cpa, cp);
> + if (ret)
> + cp_free(cp);
> +
> if (!ret)
> cp->initialized = true;
>
Hm... has this ever been correct, or did this break only with the
recent refactorings?
(IOW, what should Fixes: point to?)
next prev parent reply other threads:[~2019-07-02 8:26 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 [this message]
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
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=20190702102606.2e9cfed3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=farman@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.