Re: Tux Kernel Bug

* Marek Habersack <[email protected]> wrote:

> Yes, the oops I posted for the first time was from the older tux, I've
> tested it with the newer patches since. It seems the issue got worse,
> although the outcome is precisely the same - the machine needs to be
> hard reset in order to make it operational again. The new oops isn't a
> result of a BUG() in inode.c but a null pointer dereference, and it's
> been the same in A4 and A5:

update: found the REDIRECT_REQUEST bug too (which still triggers with
your sample module, even with the TUX_DEBUG bug fixed), the fix will be
in -A6.

	Ingo