qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/5] block: Change bdrv_get_encrypted_filename()
Date: Fri, 7 Aug 2015 16:37:06 +0200	[thread overview]
Message-ID: <55C4C292.9050904@redhat.com> (raw)
In-Reply-To: <55C2BFEA.5090800@cn.fujitsu.com>

On 06.08.2015 04:01, Wen Congyang wrote:
> On 08/06/2015 04:52 AM, Max Reitz wrote:
>> Instead of returning a pointer to the filename, copy it into a buffer
>> specified by the caller.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>>   block.c               | 24 +++++++++++++++++-------
>>   include/block/block.h |  2 +-
>>   monitor.c             |  4 +++-
>>   3 files changed, 21 insertions(+), 9 deletions(-)
>>
>> diff --git a/block.c b/block.c
>> index d088ee0..e7dd2f1 100644
>> --- a/block.c
>> +++ b/block.c
>> @@ -2760,10 +2760,12 @@ void bdrv_add_key(BlockDriverState *bs, const char *key, Error **errp)
>>           }
>>       } else {
>>           if (bdrv_key_required(bs)) {
>> +            char enc_filename[PATH_MAX];
>
> I think it's better to use g_malloc() here.
>
>> +            bdrv_get_encrypted_filename(bs, enc_filename, sizeof(enc_filename));
>>               error_set(errp, ERROR_CLASS_DEVICE_ENCRYPTED,
>>                         "'%s' (%s) is encrypted",
>>                         bdrv_get_device_or_node_name(bs),
>> -                      bdrv_get_encrypted_filename(bs));
>> +                      enc_filename);
>>           }
>>       }
>>   }
>> @@ -2980,14 +2982,22 @@ bool bdrv_can_write_zeroes_with_unmap(BlockDriverState *bs)
>>       return false;
>>   }
>>
>> -const char *bdrv_get_encrypted_filename(BlockDriverState *bs)
>> +char *bdrv_get_encrypted_filename(BlockDriverState *bs, char *dest, size_t sz)
>>   {
>> -    if (bs->backing_hd && bs->backing_hd->encrypted)
>> -        return bs->backing_file;
>> -    else if (bs->encrypted)
>> -        return bs->filename;
>> -    else
>> +    if (sz > INT_MAX) {
>> +        sz = INT_MAX;
>> +    }
>> +
>> +    if (bs->backing_hd && bs->backing_hd->encrypted) {
>> +        pstrcpy(dest, sz, bs->backing_file);
>> +        return dest;
>> +    } else if (bs->encrypted) {
>> +        pstrcpy(dest, sz, bs->filename);
>> +        return dest;
>> +    } else {
>> +        dest[0] = '\0';
>>           return NULL;
>> +    }
>>   }
>>
>>   void bdrv_get_backing_filename(BlockDriverState *bs,
>> diff --git a/include/block/block.h b/include/block/block.h
>> index 37916f7..a78e4f1 100644
>> --- a/include/block/block.h
>> +++ b/include/block/block.h
>> @@ -430,7 +430,7 @@ void bdrv_round_to_clusters(BlockDriverState *bs,
>>                               int64_t *cluster_sector_num,
>>                               int *cluster_nb_sectors);
>>
>> -const char *bdrv_get_encrypted_filename(BlockDriverState *bs);
>> +char *bdrv_get_encrypted_filename(BlockDriverState *bs, char *dest, size_t sz);
>>   void bdrv_get_backing_filename(BlockDriverState *bs,
>>                                  char *filename, int filename_size);
>>   void bdrv_get_full_backing_filename(BlockDriverState *bs,
>> diff --git a/monitor.c b/monitor.c
>> index aeea2b5..cfdf781 100644
>> --- a/monitor.c
>> +++ b/monitor.c
>> @@ -5292,10 +5292,12 @@ int monitor_read_bdrv_key_start(Monitor *mon, BlockDriverState *bs,
>>                                   BlockCompletionFunc *completion_cb,
>>                                   void *opaque)
>>   {
>> +    char enc_filename[PATH_MAX];
>
> same too.

You're right. I'll change it (in every patch of this series that pattern 
appears in).

Thanks for reviewing!

Max

>
> Thanks
> Wen Congyang
>
>>       int err;
>>
>> +    bdrv_get_encrypted_filename(bs, enc_filename, sizeof(enc_filename));
>>       monitor_printf(mon, "%s (%s) is encrypted.\n", bdrv_get_device_name(bs),
>> -                   bdrv_get_encrypted_filename(bs));
>> +                   enc_filename);
>>
>>       mon->password_completion_cb = completion_cb;
>>       mon->password_opaque = opaque;
>>
>

  reply	other threads:[~2015-08-07 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 20:52 [Qemu-devel] [PATCH v2 0/5] block: Drop BDS.filename Max Reitz
2015-08-05 20:52 ` [Qemu-devel] [PATCH v2 1/5] block: Change bdrv_get_encrypted_filename() Max Reitz
2015-08-06  2:01   ` Wen Congyang
2015-08-07 14:37     ` Max Reitz [this message]
2015-08-05 20:52 ` [Qemu-devel] [PATCH v2 2/5] block: Avoid BlockDriverState.filename Max Reitz
2015-08-06  2:27   ` Wen Congyang
2015-08-07 14:56     ` Max Reitz
2015-08-05 20:52 ` [Qemu-devel] [PATCH v2 3/5] block: Add bdrv_filename() Max Reitz
2015-08-05 20:52 ` [Qemu-devel] [PATCH v2 4/5] block: Drop BlockDriverState.filename Max Reitz
2015-08-05 20:52 ` [Qemu-devel] [PATCH v2 5/5] iotests: Test changed Quorum filename Max Reitz
2015-08-06  9:44 ` [Qemu-devel] [Qemu-block] [PATCH v2 0/5] block: Drop BDS.filename Stefan Hajnoczi

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=55C4C292.9050904@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wency@cn.fujitsu.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 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).