From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xen.org
Cc: Juergen Gross <jgross@suse.com>,
sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org, jbeulich@suse.com
Subject: [PATCH v2] docs: remove wrong statement about bug in xenstore
Date: Mon, 24 Oct 2016 15:29:35 +0200 [thread overview]
Message-ID: <1477315775-25069-1-git-send-email-jgross@suse.com> (raw)
docs/misc/xenstore.txt states that xenstored will use "0" as a valid
transaction id after 2^32 transactions. This is not true. Only
oxenstored has this bug.
Signed-off-by: Juergen Gross <jgross@suse.com>
---
v2: oxenstored has this bug
---
docs/misc/xenstore.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/docs/misc/xenstore.txt b/docs/misc/xenstore.txt
index c9f4a05..9a02b9d 100644
--- a/docs/misc/xenstore.txt
+++ b/docs/misc/xenstore.txt
@@ -229,8 +229,10 @@ TRANSACTION_START | <transid>|
tx_id request header field. When transaction is started whole
db is copied; reads and writes happen on the copy.
It is not legal to send non-0 tx_id in TRANSACTION_START.
- Currently xenstored has the bug that after 2^32 transactions
+ Currently oxenstored has the bug that after 2^32 transactions
it will allocate the transid 0 for an actual transaction.
+ xenstored (the implementation written in C) doesn't have this
+ bug.
TRANSACTION_END T|
TRANSACTION_END F|
--
2.6.6
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-10-24 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 13:29 Juergen Gross [this message]
2016-10-24 13:57 ` [PATCH v2] docs: remove wrong statement about bug in xenstore Jan Beulich
[not found] ` <580E2F560200007800119090@suse.com>
2016-10-24 14:43 ` Juergen Gross
2016-10-24 14:47 ` Wei Liu
2016-10-24 14:51 ` Juergen Gross
2016-10-24 14:59 ` Wei Liu
2016-10-24 14:58 ` Jan Beulich
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=1477315775-25069-1-git-send-email-jgross@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).