From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: ronyweng@synology.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Chage disk serial length from 20 to 36
Date: Tue, 30 Aug 2016 14:08:55 +0200 [thread overview]
Message-ID: <8737lma27c.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <7e0e5c6b-dab7-7b87-2f4d-e07c3b64cef5@redhat.com> (Paolo Bonzini's message of "Mon, 29 Aug 2016 10:25:08 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> On 29/08/2016 09:52, ronyweng@synology.com wrote:
>> From: ronyweng <ronyweng@synology.com>
>>
>> Openstack Cinder assigns volume a 36 characters uuid as serial.
>> Qemu will shrinks the uuid to 20 characters,
>> missmatch with original uuid.
>>
>> Signed-off-by: Rony Weng <ronyweng@synology.com>
>> ---
>> hw/scsi/scsi-disk.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-disk.c
>> index 836a155..0e1bb68 100644
>> --- a/hw/scsi/scsi-disk.c
>> +++ b/hw/scsi/scsi-disk.c
>> @@ -599,8 +599,8 @@ static int scsi_disk_emulate_inquiry(SCSIRequest *req, uint8_t *outbuf)
>> }
>>
>> l = strlen(s->serial);
>> - if (l > 20) {
>> - l = 20;
>> + if (l > 36) {
>> + l = 36;
>> }
>>
>> DPRINTF("Inquiry EVPD[Serial number] "
>>
>
> Cc: qemu-stable@nongnu.org
>
> Thanks, queued for 2.8 and 2.7.1
>
> Paolo
Pointing to the applicable SCSI spec chapter & verse in the commit
message would be nice. As is, 36 looks as arbitrary as 20.
next prev parent reply other threads:[~2016-08-30 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 7:52 [Qemu-devel] [PATCH] Chage disk serial length from 20 to 36 ronyweng
2016-08-29 8:25 ` Paolo Bonzini
2016-08-30 12:08 ` Markus Armbruster [this message]
2016-08-30 12:19 ` Paolo Bonzini
2016-08-30 12:44 ` Markus Armbruster
2016-08-30 15:35 ` Paolo Bonzini
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=8737lma27c.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=ronyweng@synology.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.