[Qemu-devel] [Bug 655120] [NEW] VirtFS EFAULT when accessing not existing files

[Qemu-devel] [Bug 655120] [NEW] VirtFS EFAULT when accessing not existing files

[Moshroum]

Public bug reported:

 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[Moshroum]

a good other example is tar:

$ cd /mnt
$ tar xvfj linux-2.6.35.2.tar.bz2
tar (child): bzip2: Cannot exec: Bad address
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
$ tar xvf 2.6.36-rc6.tar
2.6.36-rc6/
tar: 2.6.36-rc6: Cannot mkdir: Bad address
2.6.36-rc6/.gitignore
tar: 2.6.36-rc6/.gitignore: Cannot open: Bad address
2.6.36-rc6/.mailmap
tar: 2.6.36-rc6/.mailmap: Cannot open: Bad address
2.6.36-rc6/COPYING
tar: 2.6.36-rc6/COPYING: Cannot open: Bad address
2.6.36-rc6/CREDITS
tar: 2.6.36-rc6/CREDITS: Cannot open: Bad address
2.6.36-rc6/Documentation/
tar: 2.6.36-rc6/Documentation: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/.gitignore
tar: 2.6.36-rc6/Documentation/.gitignore: Cannot open: Bad address
2.6.36-rc6/Documentation/00-INDEX
tar: 2.6.36-rc6/Documentation/00-INDEX: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/
tar: 2.6.36-rc6/Documentation/ABI: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/ABI/README
tar: 2.6.36-rc6/Documentation/ABI/README: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/obsolete/
tar: 2.6.36-rc6/Documentation/ABI/obsolete: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/ABI/obsolete/dv1394
tar: 2.6.36-rc6/Documentation/ABI/obsolete/dv1394: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/obsolete/o2cb
tar: 2.6.36-rc6/Documentation/ABI/obsolete/o2cb: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/obsolete/sysfs-bus-usb
tar: 2.6.36-rc6/Documentation/ABI/obsolete/sysfs-bus-usb: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/obsolete/sysfs-class-rfkill
tar: 2.6.36-rc6/Documentation/ABI/obsolete/sysfs-class-rfkill: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/removed/
tar: 2.6.36-rc6/Documentation/ABI/removed: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/ABI/removed/devfs
tar: 2.6.36-rc6/Documentation/ABI/removed/devfs: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/removed/raw1394_legacy_isochronous
tar: 2.6.36-rc6/Documentation/ABI/removed/raw1394_legacy_isochronous: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/
tar: 2.6.36-rc6/Documentation/ABI/stable: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/ABI/stable/o2cb
tar: 2.6.36-rc6/Documentation/ABI/stable/o2cb: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/syscalls
tar: 2.6.36-rc6/Documentation/ABI/stable/syscalls: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/sysfs-class-backlight
tar: 2.6.36-rc6/Documentation/ABI/stable/sysfs-class-backlight: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/sysfs-class-rfkill
tar: 2.6.36-rc6/Documentation/ABI/stable/sysfs-class-rfkill: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/sysfs-class-ubi
tar: 2.6.36-rc6/Documentation/ABI/stable/sysfs-class-ubi: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/sysfs-devices-node
tar: 2.6.36-rc6/Documentation/ABI/stable/sysfs-devices-node: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/sysfs-driver-qla2xxx
tar: 2.6.36-rc6/Documentation/ABI/stable/sysfs-driver-qla2xxx: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/sysfs-driver-usb-usbtmc
tar: 2.6.36-rc6/Documentation/ABI/stable/sysfs-driver-usb-usbtmc: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/stable/sysfs-module
tar: 2.6.36-rc6/Documentation/ABI/stable/sysfs-module: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/
tar: 2.6.36-rc6/Documentation/ABI/testing: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/ABI/testing/debugfs-ec
tar: 2.6.36-rc6/Documentation/ABI/testing/debugfs-ec: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/debugfs-pktcdvd
tar: 2.6.36-rc6/Documentation/ABI/testing/debugfs-pktcdvd: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/ima_policy
tar: 2.6.36-rc6/Documentation/ABI/testing/ima_policy: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/procfs-diskstats
tar: 2.6.36-rc6/Documentation/ABI/testing/procfs-diskstats: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-block
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-block: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-css
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-css: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-i2c-devices-hm6352: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-pci
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-pci: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-pci-devices-cciss: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-umc
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-umc: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-usb
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-usb: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-c2port
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-c2port: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-bdi
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-bdi: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-lcd
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-lcd: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-led
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-led: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-mtd
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-mtd: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-pktcdvd
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-pktcdvd: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-power
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-power: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-regulator
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-regulator: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-uwb_rc
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-uwb_rc: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-dev
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-dev: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-devices
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-devices: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-memory
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-memory: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-node
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-node: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-platform-_UDC_-gadget: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-power
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-power: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-system-cpu
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-devices-system-cpu: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-driver-hid-picolcd
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-driver-hid-picolcd: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-driver-hid-prodikeys
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-driver-hid-prodikeys: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-driver-hid-roccat-kone
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-driver-hid-roccat-kone: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-acpi
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-acpi: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-memmap
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-memmap: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-sfi
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-sfi: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-sgi_uv
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-firmware-sgi_uv: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-fs-ext4
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-fs-ext4: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-gpio
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-gpio: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-i2c-bmp085
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-i2c-bmp085: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-ibft
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-ibft: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-mm
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-mm: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-mm-hugepages
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-mm-hugepages: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-slab
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-slab: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-uids
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-kernel-uids: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-memory-page-offline
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-memory-page-offline: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-ocfs2
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-ocfs2: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-platform-asus-laptop
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-platform-asus-laptop: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-platform-eeepc-laptop
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-platform-eeepc-laptop: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-power
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-power: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-pps
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-pps: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-profiling
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-profiling: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-wacom
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-wacom: Cannot open: Bad address
2.6.36-rc6/Documentation/ABI/testing/sysfs-wusb_cbaf
tar: 2.6.36-rc6/Documentation/ABI/testing/sysfs-wusb_cbaf: Cannot open: Bad address
2.6.36-rc6/Documentation/BUG-HUNTING
tar: 2.6.36-rc6/Documentation/BUG-HUNTING: Cannot open: Bad address
2.6.36-rc6/Documentation/Changes
tar: 2.6.36-rc6/Documentation/Changes: Cannot open: Bad address
2.6.36-rc6/Documentation/CodingStyle
tar: 2.6.36-rc6/Documentation/CodingStyle: Cannot open: Bad address
2.6.36-rc6/Documentation/DMA-API-HOWTO.txt
tar: 2.6.36-rc6/Documentation/DMA-API-HOWTO.txt: Cannot open: Bad address
2.6.36-rc6/Documentation/DMA-API.txt
tar: 2.6.36-rc6/Documentation/DMA-API.txt: Cannot open: Bad address
2.6.36-rc6/Documentation/DMA-ISA-LPC.txt
tar: 2.6.36-rc6/Documentation/DMA-ISA-LPC.txt: Cannot open: Bad address
2.6.36-rc6/Documentation/DMA-attributes.txt
tar: 2.6.36-rc6/Documentation/DMA-attributes.txt: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/
tar: 2.6.36-rc6/Documentation/DocBook: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/DocBook/.gitignore
tar: 2.6.36-rc6/Documentation/DocBook/.gitignore: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/Makefile
tar: 2.6.36-rc6/Documentation/DocBook/Makefile: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/alsa-driver-api.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/alsa-driver-api.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/debugobjects.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/debugobjects.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/device-drivers.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/device-drivers.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/deviceiobook.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/deviceiobook.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/drm.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/drm.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/
tar: 2.6.36-rc6/Documentation/DocBook/dvb: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/.gitignore
tar: 2.6.36-rc6/Documentation/DocBook/dvb/.gitignore: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/audio.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/audio.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/ca.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/ca.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/demux.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/demux.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/dvbapi.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/dvbapi.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/dvbproperty.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/dvbproperty.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/dvbstb.pdf
tar: 2.6.36-rc6/Documentation/DocBook/dvb/dvbstb.pdf: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/dvbstb.png
tar: 2.6.36-rc6/Documentation/DocBook/dvb/dvbstb.png: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/examples.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/examples.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/frontend.h.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/frontend.h.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/frontend.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/frontend.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/intro.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/intro.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/kdapi.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/kdapi.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/net.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/net.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/dvb/video.xml
tar: 2.6.36-rc6/Documentation/DocBook/dvb/video.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/filesystems.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/filesystems.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/gadget.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/gadget.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/genericirq.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/genericirq.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/kernel-api.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/kernel-api.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/kernel-hacking.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/kernel-hacking.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/kernel-locking.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/kernel-locking.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/kgdb.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/kgdb.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/libata.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/libata.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/librs.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/librs.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/lsm.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/lsm.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/mac80211.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/mac80211.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/mcabook.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/mcabook.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/media-entities.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/media-entities.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/media-indices.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/media-indices.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/media.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/media.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/mtdnand.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/mtdnand.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/networking.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/networking.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/rapidio.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/rapidio.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/regulator.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/regulator.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/s390-drivers.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/s390-drivers.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/scsi.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/scsi.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/sh.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/sh.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/stylesheet.xsl
tar: 2.6.36-rc6/Documentation/DocBook/stylesheet.xsl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/tracepoint.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/tracepoint.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/uio-howto.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/uio-howto.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/usb.tmpl
tar: 2.6.36-rc6/Documentation/DocBook/usb.tmpl: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/
tar: 2.6.36-rc6/Documentation/DocBook/v4l: Cannot mkdir: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/.gitignore
tar: 2.6.36-rc6/Documentation/DocBook/v4l/.gitignore: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/biblio.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/biblio.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/capture.c.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/capture.c.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/common.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/common.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/compat.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/compat.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/controls.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/controls.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/crop.gif
tar: 2.6.36-rc6/Documentation/DocBook/v4l/crop.gif: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/crop.pdf
tar: 2.6.36-rc6/Documentation/DocBook/v4l/crop.pdf: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-capture.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-capture.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-codec.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-codec.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-effect.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-effect.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-event.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-event.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-osd.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-osd.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-output.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-output.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-overlay.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-overlay.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-radio.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-radio.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-raw-vbi.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-raw-vbi.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-rds.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-rds.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-sliced-vbi.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-sliced-vbi.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/dev-teletext.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/dev-teletext.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/driver.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/driver.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/fdl-appendix.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/fdl-appendix.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_bt.gif
tar: 2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_bt.gif: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_bt.pdf
tar: 2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_bt.pdf: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_tb.gif
tar: 2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_tb.gif: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_tb.pdf
tar: 2.6.36-rc6/Documentation/DocBook/v4l/fieldseq_tb.pdf: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/func-close.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/func-close.xml: Cannot open: Bad address
2.6.36-rc6/Documentation/DocBook/v4l/func-ioctl.xml
tar: 2.6.36-rc6/Documentation/DocBook/v4l/func-ioctl.xml: Cannot open: Bad address
^C

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[Moshroum]

The untar without bz2 (second example) also happens when setting PATH to
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[Moshroum]

** Description changed:

-  use as client Debian squeeze i386 with a custom kernel:
+  use as client Debian squeeze i386 with a custom kernel:
  Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux
  
  And as host Debian squeeze amd64
  Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux
  
  kvm version is:
  kvm-88-5908-gdd67374
  
  Started the client using:
  sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic
  
  I've done following inside the guest:
+ $ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
+ $ ls -l /mnt/not-existing
+ ls: cannot access /mnt/not-existing: Bad address
+ 
+ This does not happen when not using 9p2000.L
  $ mount -t 9p -o trans=virtio host /mnt
  $ ls -l /mnt/not-existing
- ls: cannot access /mnt/not-existing: Bad address
+ ls: cannot access /mnt/not-existing: No such file or directory
  
  This return code will for example break make or many other tools.
  $ echo $PATH
  /mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  $ make KERNELDIR=/usr/src/linux
  make: execvp: pwd: Bad address
  Makefile:54: /Makefile.linux: No such file or directory
  make: *** No rule to make target `/Makefile.linux'.  Stop.

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This does not happen when not using 9p2000.L
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: No such file or directory

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[James Morse]

Reproducible here with guest kernel 2.6.36 built for i686 and qemu-kvm built from a fresh git clone taken on 27/10/2010.
Host kernel is 2.6.30.10105.2.23.fc11.i686.PAE
Guest 9p filesystem mounted as both 9p2000.u and 9p2000.L with the same problem.

In the guest syscall 'stat' on a non-existent path returns EFAULT (bad address) instead of ENOENT.
This also affects syscall 'open', and is preventing new files from being created.

I believe this is caused by 'v9fs_vfs_lookup' in 'fs/9p/vfs_inode.c' returning EFAULT instead of ENOENT.
'p9_client_walk' also returns EFAULT instead of ENOENT.
Eventually we get to 'pdu_read' in 'net/9p/protocol.c', which is being called to read '4 bytes', but calculates the space left in the 'pdu' (offset:10 size:11) as being 1. This call returns '3' (presumably how many bytes are left unread). 
In this case it gets back to 9pdu_vreadf, on line 178, (reading a 'd' 32bit integer), which sets EFAULT as the error code.

This then propagates all the way back to vfs.


This looks to me like a short-read, but I don't know enough about the plan9 filesystem protocol to be able to debug this further.


** Attachment added: "Stack trace from pdu_read"
   https://bugs.launchpad.net/qemu/+bug/655120/+attachment/1713038/+files/9p_shortread_stacktrace.txt

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This does not happen when not using 9p2000.L
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: No such file or directory

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[Venkateswararao Jujjuri (JV)]

We had a bunch of patches went into today's kernel. With those set of
patches, this problem is not reproducible.

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This does not happen when not using 9p2000.L
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: No such file or directory

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[James Morse]

Yes, I can't reproduce this anymore with the updated tree. 
This can probably be closed.

Thanks!

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This does not happen when not using 9p2000.L
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: No such file or directory

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[Moshroum]

Yes, it is a lot better... now only the complete machine crashes when
accessing the 9p.L mounted directory

{{{
virtio-9p.c:3448: submit_pdu: Assertion `!(handler == ((void *)0))' failed.
}}}

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This does not happen when not using 9p2000.L
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: No such file or directory

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[Moshroum]

** Changed in: qemu
       Status: New => Invalid

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This does not happen when not using 9p2000.L
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: No such file or directory

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.

[Qemu-devel] [Bug 655120] Re: VirtFS EFAULT when accessing not existing files

[Venkateswararao Jujjuri (JV)]

Crash indicates that the QEMU is older version. Basically client is sending something that QEMU doesn't have support on.
We have a bug opened internally to handle this situation gracefully instead of crashing. I will post the patch soon.

Moving to latest QEMU should resolve this issue...
Thanks,
JV

-- 
VirtFS EFAULT when accessing not existing files
https://bugs.launchpad.net/bugs/655120
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: Invalid

Bug description:
 use as client Debian squeeze i386 with a custom kernel:
Linux (none) 2.6.35.5 #3 Thu Sep 23 18:36:02 UTC 2010 i686 GNU/Linux

And as host Debian squeeze amd64
Linux asd 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64 GNU/Linux

kvm version is:
kvm-88-5908-gdd67374

Started the client using:
sudo /usr/local/kvm/bin/qemu-system-x86_64 -m 1024 -kernel linux-2.6.35.5.qemu -drive file=root.img,if=virtio -net nic,macaddr=02:ca:ff:ee:ba:be,model=virtio,vlan=1 -net tap,ifname=tap1,vlan=1,script=no -virtfs local,path=/host,security_model=mapped,mount_tag=host -nographic

I've done following inside the guest:
$ mount -t 9p -o trans=virtio,version=9p2000.L host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: Bad address

This does not happen when not using 9p2000.L
$ mount -t 9p -o trans=virtio host /mnt
$ ls -l /mnt/not-existing
ls: cannot access /mnt/not-existing: No such file or directory

This return code will for example break make or many other tools.
$ echo $PATH
/mnt/usr/bin:/mnt/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ make KERNELDIR=/usr/src/linux
make: execvp: pwd: Bad address
Makefile:54: /Makefile.linux: No such file or directory
make: *** No rule to make target `/Makefile.linux'.  Stop.