From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Jeff Cody <jcody@redhat.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
kwolf@redhat.com, pkrempa@redhat.com, famz@redhat.com,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 for 2.1 01/10] block: Auto-generate node_names for each BDS entry
Date: Wed, 18 Jun 2014 15:31:13 +0200 [thread overview]
Message-ID: <20140618133113.GA4424@irqsave.net> (raw)
In-Reply-To: <20140618131328.GA8856@localhost.localdomain>
The Wednesday 18 Jun 2014 à 09:13:28 (-0400), Jeff Cody wrote :
> On Wed, Jun 18, 2014 at 02:53:15PM +0200, Benoît Canet wrote:
> > The Tuesday 17 Jun 2014 à 17:53:49 (-0400), Jeff Cody wrote :
> > > Currently, node_name is only filled in when done so explicitly by the
> > > user. If no node_name is specified, then the node name field is not
> > > populated.
> > >
> > > If node_names are automatically generated when not specified, that means
> > > that all block job operations can be done by reference to the unique
> > > node_name field. This eliminates ambiguity in resolving filenames
> > > (relative filenames, or file descriptors, symlinks, mounts, etc..) that
> > > qemu currently needs to deal with.
> > >
> > > If a node name is specified, then it will not be automatically
> > > generated for that BDS entry.
> > >
> > > If it is automatically generated, it will be prefaced with "__qemu##",
> > > followed by 8 characters of a unique number, followed by 8 random
> > > ASCII characters in the range of 'A-Z'. Some sample generated node-name
> > > strings:
> > > __qemu##00000000IAIYNXXR
> > > __qemu##00000002METXTRBQ
> > > __qemu##00000001FMBORDWG
> >
> > Jeff can't we simply enforce the namespace separation with a check on the QDict
> > option content ?
> > This way we could be sure that the user can't input a node-name starting with
> > __qemu.
> >
>
> That still would not stop a user from trying to 'predict' or assuming
> what a node name would be ("oh, it is the first drive, it is probably
> __qemu##0000", etc...). Having the combination of the incrementing
> counter and the random string generation guarantees 2 things: it will
> always be unique in a qemu session, and it is not predictable by the
> user. The "__qemu##" just helps to visually identify it as a qemu
> generated.
>
> Although if you are strictly concerned about namespace confusion, we
> could enforce the namespace as you suggest, so a user could not create
> a node-name that would look like a qemu-generated node-name. Even in
> that case, I would still want to keep the sequential number + random
> string.
This way is fine for me.
>
> > >
> > > The prefix is to aid in identifying it as a qemu-generated name, the
> > > numeric portion is to guarantee uniqueness in a given qemu session, and
> > > the random characters are to further avoid any accidental collisions
> > > with user-specified node-names.
> > >
> > > Reviewed-by: Eric Blake <eblake@redhat.com>
> > > Signed-off-by: Jeff Cody <jcody@redhat.com>
> > > ---
> > > block.c | 16 +++++++++++++++-
> > > 1 file changed, 15 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/block.c b/block.c
> > > index 43abe96..da32bb0 100644
> > > --- a/block.c
> > > +++ b/block.c
> > > @@ -843,12 +843,26 @@ static int bdrv_open_flags(BlockDriverState *bs, int flags)
> > > return open_flags;
> > > }
> > >
> > > +#define GEN_NODE_NAME_PREFIX "__qemu##"
> > > +#define GEN_NODE_NAME_MAX_LEN (sizeof(GEN_NODE_NAME_PREFIX) + 8 + 8)
> > > static void bdrv_assign_node_name(BlockDriverState *bs,
> > > const char *node_name,
> > > Error **errp)
> > > {
> > > + char gen_node_name[GEN_NODE_NAME_MAX_LEN];
> > > + static uint32_t counter; /* simple counter to guarantee uniqueness */
> > > +
> > > + /* if node_name is NULL, auto-generate a node name */
> > > if (!node_name) {
> > > - return;
> > > + int len;
> > > + snprintf(gen_node_name, GEN_NODE_NAME_MAX_LEN,
> > > + "%s%08x", GEN_NODE_NAME_PREFIX, counter++);
> > > + len = strlen(gen_node_name);
> > > + while (len < GEN_NODE_NAME_MAX_LEN - 1) {
> > > + gen_node_name[len++] = g_random_int_range('A', 'Z');
> > > + }
> > > + gen_node_name[GEN_NODE_NAME_MAX_LEN - 1] = '\0';
> > > + node_name = gen_node_name;
> > > }
> > >
> > > /* empty string node name is invalid */
> > > --
> > > 1.9.3
> > >
next prev parent reply other threads:[~2014-06-18 13:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 21:53 [Qemu-devel] [PATCH v6 for 2.1 00/10] Modify block jobs to use node-names Jeff Cody
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 01/10] block: Auto-generate node_names for each BDS entry Jeff Cody
2014-06-18 12:53 ` Benoît Canet
2014-06-18 13:13 ` Jeff Cody
2014-06-18 13:31 ` Benoît Canet [this message]
2014-06-19 8:55 ` Stefan Hajnoczi
2014-06-19 12:30 ` Jeff Cody
2014-06-19 17:03 ` Eric Blake
2014-06-20 4:24 ` Stefan Hajnoczi
2014-06-23 12:41 ` Stefan Hajnoczi
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 02/10] block: add helper function to determine if a BDS is in a chain Jeff Cody
2014-06-19 6:27 ` Stefan Hajnoczi
2014-06-23 10:24 ` Benoît Canet
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 03/10] block: simplify bdrv_find_base() and bdrv_find_overlay() Jeff Cody
2014-06-19 6:31 ` Stefan Hajnoczi
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 04/10] block: make 'top' argument to block-commit optional Jeff Cody
2014-06-17 22:25 ` Eric Blake
2014-06-19 16:56 ` Eric Blake
2014-06-19 6:40 ` Stefan Hajnoczi
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 05/10] block: Accept node-name arguments for block-commit Jeff Cody
2014-06-18 12:58 ` Benoît Canet
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 06/10] block: extend block-commit to accept a string for the backing file Jeff Cody
2014-06-19 7:49 ` Stefan Hajnoczi
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 07/10] block: add ability for block-stream to use node-name Jeff Cody
2014-06-18 13:06 ` Benoît Canet
2014-06-19 8:01 ` Stefan Hajnoczi
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 08/10] block: add backing-file option to block-stream Jeff Cody
2014-06-19 8:04 ` Stefan Hajnoczi
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 09/10] block: Add QMP documentation for block-stream Jeff Cody
2014-06-19 8:06 ` Stefan Hajnoczi
2014-06-17 21:53 ` [Qemu-devel] [PATCH v6 for 2.1 10/10] block: add QAPI command to allow live backing file change Jeff Cody
2014-06-18 13:15 ` Benoît Canet
2014-06-19 8:37 ` Stefan Hajnoczi
2014-06-19 19:08 ` Jeff Cody
2014-06-19 8:37 ` Stefan Hajnoczi
2014-06-19 9:17 ` [Qemu-devel] [PATCH v6 for 2.1 00/10] Modify block jobs to use node-names Stefan Hajnoczi
2014-06-19 16:26 ` Jeff Cody
2014-06-19 16:49 ` Eric Blake
2014-06-19 16:54 ` Eric Blake
2014-06-19 18:22 ` [Qemu-devel] Op Blockers on child nodes (was Re: [PATCH v6 for 2.1 00/10] Modify block jobs to use) node-names Jeff Cody
2014-06-24 12:55 ` [Qemu-devel] [PATCH v6 for 2.1 00/10] Modify block jobs to use node-names Kevin Wolf
2014-06-23 13:08 ` Stefan Hajnoczi
2014-06-23 14:17 ` Benoît Canet
2014-06-24 2:48 ` Fam Zheng
2014-06-24 13:32 ` Jeff Cody
2014-06-24 14:08 ` Kevin Wolf
2014-06-24 15:30 ` Benoît Canet
2014-06-19 17:49 ` Benoît Canet
2014-06-24 17:08 ` Jeff Cody
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=20140618133113.GA4424@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@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).