RFC: i386: kill !4KSTACKS
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Guillaume Chazarain
Just a thought : why couldn't ndiswrapper set apart some piece of memory and use it as the stack by changing the esp register before executing windows code.
Like http://article.gmane.org/gmane.linux.drivers.ndiswrapper.general/4737
It's dirty, I know, but after all they are executing win32 code ...
Why wouldn't this work ?
I think this would be a good idea. I don't see any reason in principle why the ndiswrapper code couldn't use a separate stack for the Win32 driver code. Sharing the stack between the Linux kernel and whatever junk is going on inside the Windows driver seems rather inherently fragile..
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/