On Tue, May 15, 2007 at 04:59:49PM +0400, Vasily Averin wrote: > I would add: > I've reported about this issue some time ago to [EMAIL PROTECTED] > How this lockup can be reproduced: > - boot the kernel, > - load i2o_proc module > - login as user and read all entries in /proc/i2o/ directory > > My testnode hangs when I try to read any file from /proc/i2o/iop0/030/ > directory: I have the shell prompt and even can try to start any new command > which hangs due exec is not works. > Node is pingable, but I cannot login to it nor via ssh neither from local > console. Magic Sysrq keys are works. Kernel space software watchdog module > works OK. But all the new commnds hangs, looks like i2o controller is in coma. > > Greg KH wrote: > And I'd classify this a "low" security issue, as you have to be root to > load the i2o_proc module, and I doubt that the distros automatically > load it.
Yeah, I said it as I didn't see a "simple" way to fix it at the time. If you have solved this now with this patch, I have no objection to it. thanks, greg k-h - 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/
