aboutsummaryrefslogtreecommitdiff
path: root/docs/conf.py
diff options
context:
space:
mode:
authorChristian Schoenebeck <qemu_oss@crudebyte.com>2022-03-14 19:58:11 +0100
committerChristian Schoenebeck <qemu_oss@crudebyte.com>2022-04-30 13:11:47 +0200
commit0009df31cb51cb2be681f4eebd58a9776d75a580 (patch)
tree3bcbe880c24e525592b34b27cd7bf17b9edfb3aa /docs/conf.py
parent731340813fdb4cb8339edb8630e3f923b7d987ec (diff)
downloadqemu-0009df31cb51cb2be681f4eebd58a9776d75a580.zip
qemu-0009df31cb51cb2be681f4eebd58a9776d75a580.tar.gz
qemu-0009df31cb51cb2be681f4eebd58a9776d75a580.tar.bz2
9pfs: fix inode sequencing in 'synth' driver
The 'synth' driver's root node and the 'synth' driver's first subdirectory node falsely share the same inode number (zero), which makes it impossible for 9p clients (i.e. 9p test cases) to distinguish root node and first subdirectory from each other by comparing their QIDs (which are derived by 9p server from driver's inode numbers). Fix this issue by using prefix-increment instead of postfix-increment operator while generating new inode numbers for subdirectories and files. Link: https://lore.kernel.org/qemu-devel/3859307.hTDP4D0zbi@silver/ Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com> Reviewed-by: Greg Kurz <groug@kaod.org> Message-Id: <E1nTpyU-0000yR-9o@lizzy.crudebyte.com>
Diffstat (limited to 'docs/conf.py')
0 files changed, 0 insertions, 0 deletions