arrays allocated by the driver eat 2kB each, so a stack overflow is very
likely. Even with 8kB stack it is still not impossible. Using the version
from 2.6.5 will not be a very good idea I think, it's likely to crash your
machine one day.
:-(
The right solution would be fixing the driver to use kmalloc()/kfree() when he
really needs the memory. There was a patch only a few days ago that tried to
do that, but it was not really well done and would have crashed. If you are
really interested in I can do such a patch. The code of this driver sucks
universes through nanotubes, but one day someone _will_ have to start
cleaning this up.
Define: really interested
So, probably we are really interested. Though there are a couple of caveats:
- Testing can be done only very limited. We have only one raid array
available and it is in production
- Servers are not in yet, but will been in the next couple of weeks
- As Arjan noted the kernel will be "some vendor 2.6.5". More precisely
sles9 or rhle 3. This is dictated by the setup of informix 10 on those
machines, we are stuck with that unfortunately. To be really interesting
a patch should be backportable to 2.6.5 (or the equivalent rh kernel).
further more
- I am currently investigating if other controllers are able to support
this raid array and are supported. If so it might be a better idea to
use those
- We are willing to offer something in exchange. This ranges from 24
bottles of beer of your choice to something else. The something else
part needs to be discussed, but the beer part I can be held responsible
for :-)
Kind Regards,
B. de Bruin
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |