From: Michael Tokarev <mjt@tls.msk.ru>
To: Borislav Petkov <bp@alien8.de>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-trivial] [PATCH] memsave: Improve and disambiguate error message
Date: Tue, 10 Feb 2015 22:06:57 +0300 [thread overview]
Message-ID: <54DA56D1.9000100@msgid.tls.msk.ru> (raw)
In-Reply-To: <20150208121438.GA6290@pd.tnic>
08.02.2015 15:14, Borislav Petkov wrote:
> On Sun, Feb 08, 2015 at 11:09:24AM +0100, Paolo Bonzini wrote:
>> Cc: qemu-trivial@nongnu.org
>
> Thanks.
>
> But, there's more b0rked with this error message so you might wanna take
> the patch below instead.
>
> Btw, what are the vim settings when doing patches for qemu, this must be
> documented somewhere as coding style differs significantly from that of
> the kernel?
>
> :-)
>
> ---
> From: Borislav Petkov <bp@suse.de>
> Subject: [PATCH] memsave: Improve and disambiguate error message
>
> When requesting a size which cannot be read, the error message shows
> a different address which is misleading to the user and it looks like
> something's wrong with the address parsing. This is because the input
> @addr variable is incremented in the memory dumping loop:
Applied this version to -trivial, thank you!
/mjt
> (qemu) memsave 0xffffffff8418069c 0xb00000 mem
> Invalid addr 0xffffffff849ffe9c specified
>
> Fix that by saving the original address and size and use them in the
> error message:
>
> (qemu) memsave 0xffffffff8418069c 0xb00000 mem
> Invalid addr 0xffffffff8418069c/size 11534336 specified
>
> Cc: Anthony Liguori <aliguori@amazon.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> cpus.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/cpus.c b/cpus.c
> index 0cdd1d71560b..a5c7cad00fc9 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -1466,6 +1466,7 @@ void qmp_memsave(int64_t addr, int64_t size, const char *filename,
> uint32_t l;
> CPUState *cpu;
> uint8_t buf[1024];
> + int64_t orig_addr = addr, orig_size = size;
>
> if (!has_cpu) {
> cpu_index = 0;
> @@ -1489,7 +1490,8 @@ void qmp_memsave(int64_t addr, int64_t size, const char *filename,
> if (l > size)
> l = size;
> if (cpu_memory_rw_debug(cpu, addr, buf, l, 0) != 0) {
> - error_setg(errp, "Invalid addr 0x%016" PRIx64 "specified", addr);
> + error_setg(errp, "Invalid addr 0x%016" PRIx64 "/size %" PRId64
> + " specified", orig_addr, orig_size);
> goto exit;
> }
> if (fwrite(buf, 1, l, f) != l) {
>
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Borislav Petkov <bp@alien8.de>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] memsave: Improve and disambiguate error message
Date: Tue, 10 Feb 2015 22:06:57 +0300 [thread overview]
Message-ID: <54DA56D1.9000100@msgid.tls.msk.ru> (raw)
In-Reply-To: <20150208121438.GA6290@pd.tnic>
08.02.2015 15:14, Borislav Petkov wrote:
> On Sun, Feb 08, 2015 at 11:09:24AM +0100, Paolo Bonzini wrote:
>> Cc: qemu-trivial@nongnu.org
>
> Thanks.
>
> But, there's more b0rked with this error message so you might wanna take
> the patch below instead.
>
> Btw, what are the vim settings when doing patches for qemu, this must be
> documented somewhere as coding style differs significantly from that of
> the kernel?
>
> :-)
>
> ---
> From: Borislav Petkov <bp@suse.de>
> Subject: [PATCH] memsave: Improve and disambiguate error message
>
> When requesting a size which cannot be read, the error message shows
> a different address which is misleading to the user and it looks like
> something's wrong with the address parsing. This is because the input
> @addr variable is incremented in the memory dumping loop:
Applied this version to -trivial, thank you!
/mjt
> (qemu) memsave 0xffffffff8418069c 0xb00000 mem
> Invalid addr 0xffffffff849ffe9c specified
>
> Fix that by saving the original address and size and use them in the
> error message:
>
> (qemu) memsave 0xffffffff8418069c 0xb00000 mem
> Invalid addr 0xffffffff8418069c/size 11534336 specified
>
> Cc: Anthony Liguori <aliguori@amazon.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> cpus.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/cpus.c b/cpus.c
> index 0cdd1d71560b..a5c7cad00fc9 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -1466,6 +1466,7 @@ void qmp_memsave(int64_t addr, int64_t size, const char *filename,
> uint32_t l;
> CPUState *cpu;
> uint8_t buf[1024];
> + int64_t orig_addr = addr, orig_size = size;
>
> if (!has_cpu) {
> cpu_index = 0;
> @@ -1489,7 +1490,8 @@ void qmp_memsave(int64_t addr, int64_t size, const char *filename,
> if (l > size)
> l = size;
> if (cpu_memory_rw_debug(cpu, addr, buf, l, 0) != 0) {
> - error_setg(errp, "Invalid addr 0x%016" PRIx64 "specified", addr);
> + error_setg(errp, "Invalid addr 0x%016" PRIx64 "/size %" PRId64
> + " specified", orig_addr, orig_size);
> goto exit;
> }
> if (fwrite(buf, 1, l, f) != l) {
>
next prev parent reply other threads:[~2015-02-10 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 20:29 [Qemu-devel] [PATCH] memsave: Add a space after address in error message Borislav Petkov
2015-02-08 10:09 ` [Qemu-trivial] " Paolo Bonzini
2015-02-08 10:09 ` [Qemu-devel] " Paolo Bonzini
2015-02-08 12:14 ` [Qemu-trivial] [PATCH] memsave: Improve and disambiguate " Borislav Petkov
2015-02-08 12:14 ` [Qemu-devel] " Borislav Petkov
2015-02-08 21:46 ` [Qemu-trivial] " Paolo Bonzini
2015-02-08 21:46 ` [Qemu-devel] " Paolo Bonzini
2015-02-10 9:22 ` [Qemu-trivial] " Borislav Petkov
2015-02-10 9:22 ` [Qemu-devel] " Borislav Petkov
2015-02-10 19:06 ` Michael Tokarev [this message]
2015-02-10 19:06 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
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=54DA56D1.9000100@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aliguori@amazon.com \
--cc=bp@alien8.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 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.