http://oss.sgi.com/bugzilla/show_bug.cgi?id=411
------- Additional Comments From korn-sgi.com@xxxxxxxxxxxxxxxxxxxxxx
2008-12-27 16:26 CST -------
I definitely did run into trouble with 4k stacks elsewhere, so I no longer
enable that option in my kernels; I agree that it is conceivable that this
option was related to the problem, but what I found very distressing was that
the data rsync was transferring to xfs ended up in process names in the oops.
I'm pretty sure that isn't supposed to happen, not even when the stack flows
over. :) Couldn't it even be exploitable somehow?
I'd rather post the results of my January experiment here instead of the mailing
list, if it's okay with you, for two reasons:
1. convenience (I'm not subscribed to the list and don't have the time to follow
it anyway);
2. if someone were to search for the problem and find this bug report, they
should also immediately see what its current status is: still reproducible or
not.
My money is on it not coming up again (whatever it was, it's probably fixed by
now); however, I can't promise I'll have the time to do a really thorough test,
including enabling 4k stacks again. I'll certainly try without 4k stacks, but,
as I said, I expect everything to work this time around.
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|