>
> BTW again let me repeat this particular issue wasn't in the unwinder
> itself, but just in the fallback-to-old code which didn't do enough
> sanity checks. So you can say it's not the new unwinder that
> crashed, but the old one here. I'll add more.
I double checked this now. This case Eric ran into should be already
fixed by a patch from Jan that went in before 2.6.18 even.
He just ran with an old kernel (2.6.18-rc3) that didn't have
that particular fix.
Still the kernel stack termination is probably a good idea. I think
(haven't tested) the current 2.6.18-git* code with termination
wouldn't have crashed, but reported a (incorrect) stuck.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
