#14726 closed bug (fixed)
KDL: SMAP violation (sshfs_fuse)
Reported by: | diver | Owned by: | korli |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta2 |
Component: | File Systems/UserlandFS | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
To reproduce:
pkgman ins ssh_fuse mkdir /mnt echo password | /system/servers/userlandfs_server sshfs
In another console:
mount -t userlandfs -o 'sshfs user@server:./ -o password_stdin' /mnt
Double click newly mounted volume on the Desktop.
Attachments (3)
Change History (19)
by , 6 years ago
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Owner: | changed from | to
---|
comment:3 by , 6 years ago
diver, you can probably give more information:
Here is the help for the area debugger command: https://github.com/haiku/haiku/blob/9cc0f06a015202f58ae669f0bf7653e66161d7e2/src/system/kernel/vm/vm.cpp#L3319
"area contains <address>" should show which area is causing SMAP to trigger.
Thanks!
by , 6 years ago
comment:4 by , 6 years ago
comment:6 by , 6 years ago
Thanks! I only needed to add #include <vm/vm.h>
to make it to compile with jam userland_fs.hpkg
and now it works just fine!
comment:7 by , 6 years ago
Component: | - General → File Systems/UserlandFS |
---|
comment:10 by , 6 years ago
by , 6 years ago
comment:12 by , 6 years ago
Unfortunately no, stack trace just suddenly ends with [*** READ/WIRITE FAULT (?)]
. Running bt
about 5 times simply reboots VMware VM.
comment:13 by , 6 years ago
Please check with hrev52612 or newer.
About the stacktrace, I disabled locally print_demangled_call() in src/system/kernel/arch/x86/arch_debug.cpp to workaround the effect of SMAP. Needs more investigation.
comment:15 by , 6 years ago
For reference, the follow-up on the stacktrace problem is https://review.haiku-os.org/#/c/haiku/+/742/ (not SMAP related after all).
comment:16 by , 5 years ago
Milestone: | Unscheduled → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
I'm not sure why this ticket is assigned to me...
Anyway, I've seen the "read fault" in a backtrace only once before, in a KDL in the USB MIDI driver. Any other evidence of it? Because i have no idea where to begin investigating that.