[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <583D712F0200007800123283@prv-mh.provo.novell.com>
Date: Tue, 29 Nov 2016 04:14:39 -0700
From: "Jan Beulich" <JBeulich@...e.com>
To: "Juergen Gross" <JGross@...e.com>
Cc: <lambert.quentin@...il.com>, <jejb@...ux.vnet.ibm.com>,
<xen-devel@...ts.xenproject.org>, <boris.ostrovsky@...cle.com>,
<dan.carpenter@...cle.com>, <martin.petersen@...cle.com>,
<linux-kernel@...r.kernel.org>, <linux-scsi@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen/scsifront: don't advance ring
request pointer in case of error
>>> On 29.11.16 at 11:50, <JGross@...e.com> wrote:
> --- a/drivers/scsi/xen-scsifront.c
> +++ b/drivers/scsi/xen-scsifront.c
> @@ -184,8 +184,6 @@ static struct vscsiif_request *scsifront_pre_req(struct vscsifrnt_info *info)
>
> ring_req = RING_GET_REQUEST(&(info->ring), ring->req_prod_pvt);
>
> - ring->req_prod_pvt++;
Please note the "_pvt" suffix, which stands for "private": This field is
not visible to the backend. Only ring->sring fields are shared, and
the updating of the shared field happens in RING_PUSH_REQUESTS()
and RING_PUSH_REQUESTS_AND_CHECK_NOTIFY().
Jan
Powered by blists - more mailing lists