> This is a step in the right direction, but now cgd(4) is doing
> malloc(..., M_WAITOK) in (software) interrupt context. A LOCKDEBUG
> kernel will panic. How can we avoid the stack overflows and such in a
> different way?
Allocating buffers in softc? Buffer size is determined when cgd_ioctl_se
On Fri, Sep 11, 2009 at 09:28:34AM +, Matthias Scheler wrote:
> Module Name: src
> Committed By: tron
> Date: Fri Sep 11 09:28:34 UTC 2009
>
> Modified Files:
> src/sys/dev: cgd.c
>
> Log Message:
> Don't allocate block buffers on the stack. This can cause stack overflows
> in
On Mon, 9 Nov 2009, Christoph Egger wrote:
PR port-amiga/38335 and PR port-amiga/42174.
You mean port-alpha, right ?
Yes, I meant port-alpha. I seem to frequently mis-typing them, they
both are ingraind in my finger memory.
--
Michael L. Hitchmhi...@montana.edu
Michael L. Hitch wrote:
> Module Name: src
> Committed By: mhitch
> Date: Mon Nov 9 04:31:03 UTC 2009
>
> Modified Files:
> src/sys/arch/alpha/alpha: pmap.c
>
> Log Message:
> The tlb shootdown IPI can interrupt the pool_cache_get() in places that
> can cause a deadlock or pool ca
