b4b1561b6a
Most of the time, that is harmless and will just cause a slight delay before the vnode is removed and we return NULL instead of finding it. However, in rare circumstances involving renames, we can wind up in a deadlock with the thread that is trying to remove the vnode, and would have to wait all the way to the timeout (a full ten seconds!). The only vnodes not about to disappear from the table that can be both "removed" and "busy" seem to be special vnodes like pipes, which will be in an "unpublished" state while they are initially "busy" which we can check for, in case something wants to wait for them. The "dirconc" test readily triggered a pathological case of this behavior. Before this commit, it ran for over 15 minutes before I killed it (and it was not close to done at that point, either.) After this change, it completes successfully in around 3 minutes or so on my test VM. Thanks to mjg@freebsd.org for pointing out this testcase and its misbehavior on Haiku! Change-Id: Id1accf0aaf0724e1aec927a437d3a2ac1596cd98
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.