> Horst von Brand <firstname.lastname@example.org> writes:
>> Boots and panics immediately "trying to kill init"
> Backout the changes to fs/locks.c or the patch of Trond :
Huh? WTF does a patch to the locking code have to do with init?
That particular code is only called if something closes a file on
which POSIX locks are applied. Init doesn't use locking.
The patch *is* required in Alan's tree. Without it, 2 processes that
lock the same file can race and corrupt the i_flock list.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/