On 6/3/07, Arjan van de Ven <[email protected]> wrote:
On Fri, 2007-06-01 at 12:47 -0500, Matthew Fredrickson wrote:
> My question is this: is there a way to either work around the problem I
> am seeing with the stack without recompiling the kernel with 8K stack
> size or without disabling irqs for such a long period of time (which I
> think is not a nice thing to do either) OR is it acceptable (although
> not nice) to simply fix it this way, by disabling irqs while it loads
> the firmware?
I wonder if you're chasing ghosts; 4K stack kernels have a seperate
stack for interrupts so... those should be safe.
Argh, yes, thanks for reminding/correcting all of us :-)
Btw, you forgot to post a pointer to the source code of your driver, so
it's a lot harder for us (read: impossible) to give you good advice..
Right, and dmesg / debug output of when things go wrong is also
needed at the very least to confirm whether or not there is really a
stack overflow issue here in the first place.
Satyam
-
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]
