|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v3] docs: remove wrong statement about bug in xenstore
docs/misc/xenstore.txt states that xenstored will use "0" as a valid
transaction id after 2^32 transactions. This is not true. Remove that
statement.
Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
---
v3: rephrase oxenstored part as suggested by Wei Liu
v2: oxenstored has this bug
---
docs/misc/xenstore.txt | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/misc/xenstore.txt b/docs/misc/xenstore.txt
index c9f4a05..a0207f1 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
- it will allocate the transid 0 for an actual transaction.
+ Currently oxenstored has the bug that after the internal
+ representation of transaction id gets overflowed, 0 is returned.
+ 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@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |