From: Eric Blake <eblake@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Aleksandar Markovic <amarkovic@wavecomp.com>,
qemu-block@nongnu.org, qemu-trivial@nongnu.org,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH v2 3/3] trace: Forbid dynamic field width in event format
Date: Fri, 8 Nov 2019 10:07:38 -0600 [thread overview]
Message-ID: <191fbe18-73b2-4d22-5540-8775688166a8@redhat.com> (raw)
In-Reply-To: <20191108144042.30245-4-philmd@redhat.com>
On 11/8/19 8:40 AM, Philippe Mathieu-Daudé wrote:
> Since not all trace backends support dynamic field width in
> format (dtrace via stap does not), forbid them.
>
> Add a check to refuse field width in new formats:
>
> +++ b/scripts/tracetool/__init__.py
> @@ -206,6 +206,7 @@ class Event(object):
> "\s*"
> "(?:(?:(?P<fmt_trans>\".+),)?\s*(?P<fmt>\".+))?"
> "\s*")
> + _DFWRE = re.compile(".*(%0?\*).*")
The use of leading and trailing .* is pointless if the RE itself is used
unanchored and where you only care if the () matched.
This doesn't catch all valid uses of * in a printf format. Better might
be something like:
_DFWRE = re.compile("%[\d\.\- +#']*\*")
which matches only if there is a %, any number of characters that can
form a printf flag, as well as a numeric field width but dynamic precision.
> + if Event._DFWRE.match(fmt):
> + raise ValueError("Event format must not contain field width '%*'")
>
> if len(fmt_trans) > 0:
> fmt = [fmt_trans, fmt]
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-11-08 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 14:40 [PATCH v2 0/3] hw: Remove dynamic field width from trace events Philippe Mathieu-Daudé
2019-11-08 14:40 ` [PATCH v2 1/3] hw/block/pflash: " Philippe Mathieu-Daudé
2019-11-08 15:56 ` Eric Blake
2019-11-14 21:26 ` Philippe Mathieu-Daudé
2019-11-18 19:21 ` Eric Blake
2019-11-18 20:39 ` Philippe Mathieu-Daudé
2019-11-08 14:40 ` [PATCH v2 2/3] hw/mips/gt64xxx: " Philippe Mathieu-Daudé
2019-11-08 15:58 ` Eric Blake
2019-11-14 21:24 ` Philippe Mathieu-Daudé
2019-11-18 19:10 ` Philippe Mathieu-Daudé
2019-11-18 19:15 ` Eric Blake
2019-11-08 14:40 ` [PATCH v2 3/3] trace: Forbid dynamic field width in event format Philippe Mathieu-Daudé
2019-11-08 16:07 ` Eric Blake [this message]
2019-11-18 18:42 ` Eric Blake
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=191fbe18-73b2-4d22-5540-8775688166a8@redhat.com \
--to=eblake@redhat.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@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).