Opened 10 years ago

Closed 10 years ago

#10244 closed bug (fixed)

Haikuporter KDLs when building WebKit recipe

Reported by: pulkomandy Owned by: bonefish
Priority: normal Milestone: R1
Component: File Systems/bindfs Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

Trying to create a file in /port/develop/headers in the chroot results in a KDL in installation phase. See attached picture.

(do we need a "File Systems/chroot" component ?)

Attachments (1)

P1010226.JPG​ (2.3 MB ) - added by pulkomandy 10 years ago.
KDL screenshot.

Change History (6)

by pulkomandy, 10 years ago

Attachment: P1010226.JPG​ added

KDL screenshot.

comment:1 by anevilyak, 10 years ago

Component: File Systems → System/Kernel
Status: new → assigned

chroot is a VFS function rather than a standalone filesystem. In any case, it'd be helpful to have the actual panic message too, as that's been cut off in the screenshot.

comment:2 by bonefish, 10 years ago

Given that a bindfs is mounted at /port, this might not even be related to the chroot.

As a side note, a recipe has no business creating files anywhere in /port.

comment:3 by bonefish, 10 years ago

Component: System/Kernel → File Systems

Confirmed to be a bindfs issue. Can be easily reproduced: 

~> mkdir source target
~> mount -t bindfs -p "source /boot/home/source" target
~> touch target/xx

The panic message is: 

PANIC: vfs: fs_create() returned success but there is no vnode, mount ID 8!

comment:4 by bonefish, 10 years ago

Component: File Systems → File Systems/bindfs

comment:5 by bonefish, 10 years ago

Resolution: → fixed
Status: assigned → closed

Fixed in hrev46446.

Note: See TracTickets for help on using tickets.