From: On Behalf Of Alan Cox
> I don't think so. The bug as such is something I can only see being
> triggerable either by a virtual machine or by something like serious
> noise on the signal lines (eg put a 10Khz carrier on the
> carrier detect
> line)
We found and patched this bug in one of our products. The patch was to
raise the loop counter to something more appropriate for our hardware.
The condition: the not-to-speedy embedded CPU and all ports in use.
The interrupt handler would hit the loop limit because the combination
of all ports running meant usually there was one port that needed
servicing, upping the loop count by one.
..Stu
-
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]
