On 4/13/05, Eugene Surovegin <ebs at ebshome.net> wrote: > Then do it. It should be trivial to unwind the stack and much simpler > than moving this code to process context.
Actually, Im not too sure what is required to put something in kernel in process context. Maybe its alot harder than I think it is... > I think it's a bad idea. You are trying to workaround a problem > instead of fixing it. My experience shows that sooner or later it'll > come back and hit you anyway :). I'm with you on this. It just that I didnt think putting my code in process context would be regarded as workaround. Since kernel itself ran fine, only after putting in my change it caused problem, I simply thought that putting changes to code that was already there is more severe than making further changes to what I've done. At least this way, change is still within my domain. But again, if putting my function in process context is that hard.. okay I better think otherwise :) -- Daniel
