Dynamic translator stacks are set in series of retries

When a client wants nsmux to set several translators on a node
using a syntax like ``file,,x,,y'', nsmux sets the first
translator on a shadow node mirroring ``file'' and punts a
retry to the client. The client (commonly) does the retry and
thus control comes back to nsmux, which creates another shadow
node and sets the second translator on this node.

At the moment translator stacks do not include proxy nodes, i.e.
the structure of a dynamic translator stack is:

...---dynamic translator -- shadow node -- dynamic translator ---...

1 files changed, 1 insertions, 1 deletions

diff --git a/node.h b/node.h
index 89de42118..9ae760f01 100644
--- a/node.h
+++ b/node.h
@@ -37,7 +37,7 @@
 /*---------------------------------------------------------------------------*/
 /*--------Macros-------------------------------------------------------------*/
 /*Checks whether the give node is the root of the proxy filesystem*/
-#define NODE_IS_ROOT(n) (((n)->nn->lnode->dir) ? (0) : (1))
+#define NODE_IS_ROOT(n) (((n)->nn->lnode && (n)->nn->lnode->dir) ? (0) : (1))
 /*---------------------------------------------------------------------------*/
 /*Node flags*/
 #define FLAG_NODE_ULFS_FIXED    0x00000001 /*this node should not be updated */