aboutsummaryrefslogtreecommitdiff
path: root/hw/9pfs/coth.c
diff options
context:
space:
mode:
authorGreg Kurz <groug@kaod.org>2016-08-30 17:02:27 +0200
committerPeter Maydell <peter.maydell@linaro.org>2016-08-30 19:23:00 +0100
commit56f101ecce0eafd09e2daf1c4eeb1377d6959261 (patch)
tree9b7c8ceb972c7a4da49bee92fff49939376e35a1 /hw/9pfs/coth.c
parent805b5d98c649d26fc44d2d7755a97f18e62b438a (diff)
downloadqemu-56f101ecce0eafd09e2daf1c4eeb1377d6959261.zip
qemu-56f101ecce0eafd09e2daf1c4eeb1377d6959261.tar.gz
qemu-56f101ecce0eafd09e2daf1c4eeb1377d6959261.tar.bz2
9pfs: handle walk of ".." in the root directory
The 9P spec at http://man.cat-v.org/plan_9/5/intro says: All directories must support walks to the directory .. (dot-dot) meaning parent directory, although by convention directories contain no explicit entry for .. or . (dot). The parent of the root directory of a server's tree is itself. This means that a client cannot walk further than the root directory exported by the server. In other words, if the client wants to walk "/.." or "/foo/../..", the server should answer like the request was to walk "/". This patch just does that: - we cache the QID of the root directory at attach time - during the walk we compare the QID of each path component with the root QID to detect if we're in a "/.." situation - if so, we skip the current component and go to the next one Signed-off-by: Greg Kurz <groug@kaod.org> Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'hw/9pfs/coth.c')
0 files changed, 0 insertions, 0 deletions