From: Kevin Wolf <kwolf@redhat.com>
To: Shahar Havivi <shaharh@redhat.com>
Cc: Luiz Capitulino <lcapitul@redhat.com>,
Dor Laor <dlaor@redhat.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Wrong error message in block_passwd command
Date: Fri, 05 Mar 2010 16:22:55 +0100 [thread overview]
Message-ID: <4B9121CF.6020703@redhat.com> (raw)
In-Reply-To: <20100305151222.GA21283@redhat.com>
Am 05.03.2010 16:12, schrieb Shahar Havivi:
> Monitor command 'block_passwd' reports a wrong error message when
> drive is not encrypted
>
> Signed-off-by: Shahar Havivi <shaharh@redhat.com>
> ---
> block.c | 9 ++++++---
> monitor.c | 7 ++++++-
> qerror.c | 4 ++++
> qerror.h | 3 +++
> 4 files changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/block.c b/block.c
> index 31d1ba4..dd484fa 100644
> --- a/block.c
> +++ b/block.c
> @@ -1132,10 +1132,13 @@ int bdrv_set_key(BlockDriverState *bs, const char *key)
> if (ret < 0)
> return ret;
> if (!bs->encrypted)
> - return 0;
> + return -EINVAL;
> + }
I think this part is wrong actually. Sorry for not catching it when you
sent me the patch first.
The logic here is that it's not an error to set the password for a file
which isn't encrypted itself, but its backing file is. In this case the
key is only set for the backing file and we return success.
The other parts look good to me.
Kevin
next prev parent reply other threads:[~2010-03-05 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 15:12 [Qemu-devel] [PATCH] Wrong error message in block_passwd command Shahar Havivi
2010-03-05 15:22 ` Kevin Wolf [this message]
2010-03-05 15:47 ` [Qemu-devel] " Shahar Havivi
2010-03-05 15:56 ` Luiz Capitulino
2010-03-05 16:47 ` Markus Armbruster
2010-03-05 20:41 ` Luiz Capitulino
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=4B9121CF.6020703@redhat.com \
--to=kwolf@redhat.com \
--cc=dlaor@redhat.com \
--cc=lcapitul@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shaharh@redhat.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).