On Sat, Nov 19, 2005 at 10:04:11PM +0100, Thomas Graf wrote:
>
> The continued dumps wouldn't be the problem, the walker is allocated
> on the initial dump call. It was a mistake though, nlk->cb_lock spin
> lock is always held for cb->dump() even though it should only be
> required during the nlk-
* Herbert Xu <[EMAIL PROTECTED]> 2005-11-19 22:48
> Thomas Graf <[EMAIL PROTECTED]> wrote:
> >
> > I did. I think it was right, why would an allocation be necessary on
> > the second call to inet6_dump_fib()? The walker allocated in process
> > context on the first call should be reused from cb->a
Thomas Graf <[EMAIL PROTECTED]> wrote:
>
> I did. I think it was right, why would an allocation be necessary on
> the second call to inet6_dump_fib()? The walker allocated in process
> context on the first call should be reused from cb->args[0].
Continued dumps are always called under spin lock (
* YOSHIFUJI Hideaki / ?$B5HF#1QL@ <[EMAIL PROTECTED]> 2005-11-18 09:47
> In article <[EMAIL PROTECTED]> (at Fri, 18 Nov 2005 08:44:27 +0800), Yan
> Zheng <[EMAIL PROTECTED]> says:
>
> > I get follow message when switch to single user mode and the kernel version
> > is 2.6.15-rc1-git5.
> :
> > No
In article <[EMAIL PROTECTED]> (at Fri, 18 Nov 2005 08:44:27 +0800), Yan Zheng
<[EMAIL PROTECTED]> says:
> I get follow message when switch to single user mode and the kernel version
> is 2.6.15-rc1-git5.
:
> Nov 18 08:26:23 localhost kernel: Debug: sleeping function called from
> invalid conte
I get follow message when switch to single user mode and the kernel version is
2.6.15-rc1-git5.
Regards
Nov 18 08:26:23 localhost kernel: Debug: sleeping function called from invalid
context at mm/slab.c:2472
Nov 18 08:26:23 localhost kernel: in_atomic():1, irqs_disabled():0
Nov 18 08:26:23 lo
