From: Jeff Cody <jcody@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
armbru@redhat.com, programmingkidx@gmail.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/2] util - add automated ID generation utility
Date: Tue, 1 Sep 2015 20:08:21 -0400 [thread overview]
Message-ID: <20150902000821.GH2669@localhost.localdomain> (raw)
In-Reply-To: <55E62CD4.9060309@redhat.com>
On Tue, Sep 01, 2015 at 04:55:16PM -0600, Eric Blake wrote:
> On 09/01/2015 04:30 PM, Jeff Cody wrote:
> > Multiple sub-systems in QEMU may find it useful to generate IDs
> > for objects that a user may reference via QMP or HMP. This patch
> > presents a standardized way to do it, so that automatic ID generation
> > follows the same rules.
> >
> > This patch enforces the following rules when generating an ID:
> >
> > 1.) Guarantee no collisions with a user-specified ID
> > 2.) Identify the sub-system the ID belongs to
> > 3.) Guarantee of uniqueness
> > 4.) Spoiling predictability, to avoid creating an assumption
> > of object ordering and parsing (i.e., we don't want users to think
> > they can guess the next ID based on prior behavior).
> >
> > The scheme for this is as follows (no spaces):
> >
> > # subsys D RR
> > Reserved char --| | | |
> > Subsystem String ----| | |
> > Unique number (64-bit) --| |
> > Two-digit random number ---|
> >
> > For example, a generated node-name for the block sub-system may look
> > like this:
> >
> > #block076
> >
> > The caller of id_generate() is responsible for freeing the generated
> > node name string with g_free().
> >
> > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > ---
> > include/qemu-common.h | 8 ++++++++
> > util/id.c | 36 ++++++++++++++++++++++++++++++++++++
> > 2 files changed, 44 insertions(+)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> > +
> > +static const char * const id_subsys_str[] = {
> > + [ID_QDEV] = "qdev",
> > + [ID_BLOCK] = "block",
> > +};
>
> We're inconsistent on whether there should be a space in '*const'
> (compare commit a91e211 with b86f461, for example). But since qemu.git
> has both spellings in various contexts, it's probably not worth changing
> here.
>
If this ends up needing another rev, I'll change it for you :)
> > +
> > + rnd = g_random_int_range(0, 99);
>
> Thankfully, g_random_* is a PRNG that is not consuming system entropy
> (auto-generated names should not be starving /dev/random).
>
Yup.
Thanks,
Jeff
next prev parent reply other threads:[~2015-09-02 0:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 22:30 [Qemu-devel] [PATCH v2 0/2] Auto-generated IDs Jeff Cody
2015-09-01 22:30 ` [Qemu-devel] [PATCH v2 1/2] util - add automated ID generation utility Jeff Cody
2015-09-01 22:55 ` Eric Blake
2015-09-02 0:08 ` Jeff Cody [this message]
2015-09-02 0:13 ` John Snow
2015-09-02 6:35 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2015-09-03 14:47 ` Jeff Cody
2015-09-18 12:58 ` [Qemu-devel] " Markus Armbruster
2015-09-01 22:30 ` [Qemu-devel] [PATCH v2 2/2] block: auto-generated node-names Jeff Cody
2015-09-18 13:03 ` Markus Armbruster
2015-09-03 15:02 ` [Qemu-devel] [PATCH v2 0/2] Auto-generated IDs Kevin Wolf
2015-09-03 15:54 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2015-09-18 13:06 ` [Qemu-devel] " 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=20150902000821.GH2669@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=programmingkidx@gmail.com \
--cc=qemu-block@nongnu.org \
--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 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).