qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: john cooper <john.cooper@redhat.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Marc Haber <mh+qemu-devel@zugschlus.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/4] Add virtio disk identification support
Date: Fri, 04 Jun 2010 16:45:09 +0200	[thread overview]
Message-ID: <4C091175.4010102@redhat.com> (raw)
In-Reply-To: <4C07FDE3.3020905@codemonkey.ws>

Am 03.06.2010 21:09, schrieb Anthony Liguori:
> On 03/25/2010 12:32 AM, john cooper wrote:
>> Add virtio-blk device id (s/n) support via virtio request.
>> Remove artifacts of pci and ATA_IDENTIFY implementation
>> relative to prior versions.
>>
>> Signed-off-by: john cooper<john.cooper@redhat.com>
>> ---
>>
>> diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
>> index 9915840..358b0af 100644
>> --- a/hw/virtio-blk.c
>> +++ b/hw/virtio-blk.c
>> @@ -19,6 +19,8 @@
>>   # include<scsi/sg.h>
>>   #endif
>>
>> +#define min(a,b) ((a)<  (b) ? (a) : (b))
>>    
> 
> We already have MIN().
> 
>> +
>>   typedef struct VirtIOBlock
>>   {
>>       VirtIODevice vdev;
>> @@ -28,6 +30,7 @@ typedef struct VirtIOBlock
>>       QEMUBH *bh;
>>       BlockConf *conf;
>>       unsigned short sector_mask;
>> +    char sn[BLOCK_SERIAL_STRLEN];
>>   } VirtIOBlock;
>>
>>   static VirtIOBlock *to_virtio_blk(VirtIODevice *vdev)
>> @@ -317,6 +320,12 @@ static void virtio_blk_handle_request(VirtIOBlockReq *req,
>>           virtio_blk_handle_flush(req);
>>       } else if (req->out->type&  VIRTIO_BLK_T_SCSI_CMD) {
>>           virtio_blk_handle_scsi(req);
>> +    } else if (req->out->type&  VIRTIO_BLK_T_GET_ID) {
>> +        VirtIOBlock *s = req->dev;
>> +
>> +        memcpy(req->elem.in_sg[0].iov_base, s->sn,
>> +               min(req->elem.in_sg[0].iov_len, sizeof(s->sn)));
>> +        virtio_blk_req_complete(req, VIRTIO_BLK_S_OK);
>>       } else if (req->out->type&  VIRTIO_BLK_T_OUT) {
>>           qemu_iovec_init_external(&req->qiov,&req->elem.out_sg[1],
>>                                    req->elem.out_num - 1);
>> @@ -496,6 +505,8 @@ VirtIODevice *virtio_blk_init(DeviceState *dev, BlockConf *conf)
>>       bdrv_guess_geometry(s->bs,&cylinders,&heads,&secs);
>>       bdrv_set_geometry_hint(s->bs, cylinders, heads, secs);
>>
>> +    strncpy(s->sn, drive_get_serial(s->bs), sizeof (s->sn));
>> +
>>    
> 
> Friends don't let friends use strncpy().
> 
> This actually will result in a non-NULL terminated string if 
> drive_get_serial() returns a string larger than s->sn.  Use snprintf() 
> instead.

Isn't this what we have pstrcpy for?

Kevin

      parent reply	other threads:[~2010-06-04 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  5:32 [Qemu-devel] [PATCH 1/4] Add virtio disk identification support john cooper
2010-06-03 19:09 ` [Qemu-devel] " Anthony Liguori
2010-06-04  6:32   ` john cooper
2010-06-04 14:45   ` Kevin Wolf [this message]

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=4C091175.4010102@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=john.cooper@redhat.com \
    --cc=mh+qemu-devel@zugschlus.de \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    /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).