On 10/1/06, Andi Kleen <[email protected]> wrote:
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.
Hmm, not sure I'm following you, but I did try with the released
v2.6.18 (fourth stacktrace in my first email in this thread). The
2.6.13-rc3 (d94a041519f3ab1ac023bf917619cd8c4a7d3c01) version was
tested only as the result of git-bisect, and is the first kernel that
crashed in this way. But v2.6.18 crashed in a similar way as well.
Are you saying v2.6.18 should contain a fix preventing it from crashing?
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.
Making sure my post was clear: that's what v2.6.18 + termination does.
Sorry if I misunderstood you.
er.
-
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]
