From: Markus Armbruster <armbru@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Pavel Dovgalyuk <Pavel.Dovgaluk@ispras.ru>
Subject: Re: [Qemu-devel] [PATCH] coverity-model: replay data is considered trusted
Date: Tue, 15 May 2018 14:00:38 +0200 [thread overview]
Message-ID: <87r2md6sd5.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20180514141218.28438-1-pbonzini@redhat.com> (Paolo Bonzini's message of "Mon, 14 May 2018 16:12:18 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> Replay data is not considered a possible attack vector; add a model that
> does not use getc so that "tainted data" warnings are suppressed.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> scripts/coverity-model.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/scripts/coverity-model.c b/scripts/coverity-model.c
> index c702804f41..576f48de33 100644
> --- a/scripts/coverity-model.c
> +++ b/scripts/coverity-model.c
> @@ -103,6 +103,19 @@ static int get_keysym(const name2keysym_t *table,
/* Tainting */
typedef struct {} name2keysym_t;
static int get_keysym(const name2keysym_t *table,
const char *name)
{
int result;
if (result > 0) {
__coverity_tainted_string_sanitize_content__(name);
return result;
} else {
return 0;
> }
> }
>
> +
Does the new model go under /* Tainting */ ?
If yes, I'd like to have just one blank line here.
> +/* Replay data is considered trusted. */
If no, I'd like to insert one here.
> +uint8_t replay_get_byte(void)
> +{
> + uint8_t byte = 0;
> + if (replay_file) {
> + uint8_t c;
> + byte = c;
> + }
> + return byte;
> +}
> +
> +
> /*
> * GLib memory allocation functions.
> *
next prev parent reply other threads:[~2018-05-15 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 14:12 [Qemu-devel] [PATCH] coverity-model: replay data is considered trusted Paolo Bonzini
2018-05-14 14:14 ` no-reply
2018-05-15 12:00 ` Markus Armbruster [this message]
2018-05-15 12:06 ` Paolo Bonzini
2018-05-15 14:33 ` Markus Armbruster
2018-06-26 7:27 ` Markus Armbruster
2018-06-26 7:55 ` Paolo Bonzini
2018-06-26 8:55 ` Markus Armbruster
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=87r2md6sd5.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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.