aboutsummaryrefslogtreecommitdiffstats
path: root/tools/xenstore/xenstored_watch.c
diff options
context:
space:
mode:
authorcl349@firebug.cl.cam.ac.uk <cl349@firebug.cl.cam.ac.uk>2005-09-14 08:41:49 +0000
committercl349@firebug.cl.cam.ac.uk <cl349@firebug.cl.cam.ac.uk>2005-09-14 08:41:49 +0000
commit2c0ba8d0753536c7cd9651b0326bcfabd2d20e18 (patch)
tree0f0239dde301f60a31c0d4232bf33c4d1b807618 /tools/xenstore/xenstored_watch.c
parentab4b7e8e65a86fef5f352932f99bfe6415c1b06c (diff)
downloadxen-2c0ba8d0753536c7cd9651b0326bcfabd2d20e18.tar.gz
xen-2c0ba8d0753536c7cd9651b0326bcfabd2d20e18.tar.bz2
xen-2c0ba8d0753536c7cd9651b0326bcfabd2d20e18.zip
Fix xenstored watch crash.
When a connection blocked waiting on a transaction, don't queue watch events. Sure, they'd be ignored and re-transmitted, but it hits an assert that we don't send data out blocked connections, and it's wasteful. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (authored) Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Diffstat (limited to 'tools/xenstore/xenstored_watch.c')
-rw-r--r--tools/xenstore/xenstored_watch.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/xenstore/xenstored_watch.c b/tools/xenstore/xenstored_watch.c
index e40318ee2f..a543f8a495 100644
--- a/tools/xenstore/xenstored_watch.c
+++ b/tools/xenstore/xenstored_watch.c
@@ -144,7 +144,7 @@ void fire_watches(struct connection *conn, const char *node, bool recurse)
else
continue;
/* If connection not doing anything, queue this. */
- if (!i->out)
+ if (i->state == OK)
queue_next_event(i);
}
}