From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: lambert.quentin@gmail.com, linux-scsi@vger.kernel.org,
dan.carpenter@oracle.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com
Subject: Re: [PATCH v2] xen/scsifront: don't request a slot on the ring until request is ready
Date: Mon, 5 Dec 2016 16:35:13 +0100 [thread overview]
Message-ID: <2f607bd6-f058-34bd-fb92-642e78ee283e@suse.com> (raw)
In-Reply-To: <6cbdced5-c4fe-8083-3a90-09c428f3ff8f@oracle.com>
On 05/12/16 16:32, Boris Ostrovsky wrote:
> On 12/02/2016 01:15 AM, Juergen Gross wrote:
>>
>> -static struct vscsiif_request *scsifront_pre_req(struct vscsifrnt_info *info)
>> +static int scsifront_do_request(struct vscsifrnt_info *info,
>> + struct vscsifrnt_shadow *shadow)
>> {
>> struct vscsiif_front_ring *ring = &(info->ring);
>> struct vscsiif_request *ring_req;
>> + struct scsi_cmnd *sc = shadow->sc;
>> uint32_t id;
>> + int i, notify;
>> +
>> + if (RING_FULL(&info->ring))
>> + return -EBUSY;
>>
>> id = scsifront_get_rqid(info); /* use id in response */
>> if (id >= VSCSIIF_MAX_REQS)
>> - return NULL;
>> + return -EBUSY;
>> +
>> + info->shadow[id] = shadow;
>> + shadow->rqid = id;
>>
>> ring_req = RING_GET_REQUEST(&(info->ring), ring->req_prod_pvt);
>> -
>> ring->req_prod_pvt++;
>>
>> - ring_req->rqid = (uint16_t)id;
>> + ring_req->rqid = id;
>> + ring_req->act = shadow->act;
>> + ring_req->ref_rqid = shadow->ref_rqid;
>> + ring_req->nr_segments = shadow->nr_segments;
>
> Shouldn't req_prod_pvt be incremented after you've copied everything? (I
> realize that there is not error until everything has been copied but still.)
That doesn't really matter as it is private.
>> @@ -473,44 +496,14 @@ static int map_data_for_request(struct vscsifrnt_info *info,
>> }
>>
>> if (seg_grants)
>> - ring_req->nr_segments = VSCSIIF_SG_GRANT | seg_grants;
>> + shadow->nr_segments = VSCSIIF_SG_GRANT | seg_grants;
>
> Are we guaranteed that seg_grants is not going to have VSCSIIF_SG_GRANT
> bit set?
Absolutely, yes. Can't be larger than VSCSIIF_SG_TABLESIZE which is 26.
Juergen
next prev parent reply other threads:[~2016-12-05 15:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 18:22 [PATCH] xen-scsifront: Add a missing call to kfree Quentin Lambert
2016-11-21 6:01 ` Juergen Gross
2016-11-22 3:40 ` Martin K. Petersen
2016-11-22 5:19 ` Juergen Gross
2016-11-25 21:28 ` Dan Carpenter
2016-11-29 10:50 ` [PATCH] xen/scsifront: don't advance ring request pointer in case of error Juergen Gross
2016-11-29 11:14 ` [Xen-devel] " Jan Beulich
[not found] ` <583D712F0200007800123283@suse.com>
2016-11-29 11:19 ` Juergen Gross
2016-11-29 11:28 ` David Vrabel
2016-11-29 11:33 ` Juergen Gross
2016-11-29 11:40 ` Jan Beulich
[not found] ` <583D772D02000078001232DD@suse.com>
2016-11-29 12:33 ` Juergen Gross
2016-12-02 6:10 ` [PATCH v2] xen/scsifront: don't request a slot on the ring until request is ready Juergen Gross
2016-12-02 6:13 ` Juergen Gross
2016-12-02 6:15 ` Juergen Gross
2016-12-05 15:32 ` Boris Ostrovsky
2016-12-05 15:35 ` Juergen Gross [this message]
2016-12-08 14:56 ` Boris Ostrovsky
2016-12-09 10:13 ` Juergen Gross
2016-12-05 20:53 ` [PATCH] xen-scsifront: Add a missing call to kfree Dan Carpenter
2016-12-06 5:45 ` Juergen Gross
2016-12-06 10:22 ` Dan Carpenter
2016-11-24 8:24 ` Juergen Gross
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=2f607bd6-f058-34bd-fb92-642e78ee283e@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dan.carpenter@oracle.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=lambert.quentin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=xen-devel@lists.xenproject.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®