Thomas Veerman 230ea1ce13 VFS: remove erroneous assert
The assert was meant as an additional check to the assert in link.c:198.
The reasoning behind the assert in link.c:198 is that once you've
obtained a write lock on a vmnt, you can't get an additional read lock
on the same vmnt. However, that does not always hold for the assert in
path.c:281 where the situation could be that you've obtained a read lock
and managed to get another read lock (this is possible). In other words,
the assert in path.c:281 is not the right place to check for that
situation.
2012-02-20 09:17:42 +00:00
2010-10-25 08:32:14 +00:00
2012-02-17 23:53:44 +01:00
2011-11-18 11:11:04 +01:00
2012-02-18 02:05:04 +01:00
2012-02-18 01:17:32 +01:00
2012-02-17 12:32:35 +00:00
2012-02-16 01:48:46 +00:00
2012-02-20 09:17:42 +00:00
2012-02-17 17:22:37 +00:00
2012-02-17 12:32:35 +00:00
2010-01-21 10:16:05 +00:00
Description
A fun microkernel meant to match modern usecases
GPL-3.0 148 MiB
Languages
C 78.2%
Roff 10.2%
Assembly 4.6%
Shell 3.7%
Makefile 1.6%
Other 1.2%