[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080331.030848.175668431.davem@davemloft.net>
Date: Mon, 31 Mar 2008 03:08:48 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mingo@...e.hu
Cc: dada1@...mosbay.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl
Subject: Re: [RFC,PATCH] loopback: calls netif_receive_skb() instead of
netif_rx()
From: Ingo Molnar <mingo@...e.hu>
Date: Mon, 31 Mar 2008 11:48:23 +0200
>
> * Eric Dumazet <dada1@...mosbay.com> wrote:
>
> > I noticed some paths in kernel are very stack aggressive, and on i386
> > with CONFIG_4KSTACKS we were really in a dangerous land, even without
> > my patch.
> >
> > What we call 4K stacks is in fact 4K - sizeof(struct task_struct), so
> > a litle bit more than 2K. [...]
>
> that's just wrong - 4K stacks on x86 are 4K-sizeof(thread_info) - the
> task struct is allocated elsewhere. The patch below runs just fine on
> 4K-stack x86.
I don't think it's safe.
Every packet you receive can result in a sent packet, which
in turn can result in a full packet receive path being
taken, and yet again another sent packet.
And so on and so forth.
Some cases like this would be stack bugs, but wouldn't
you like that bug to be a very busy cpu instead of a
crash from overrunning the current stack?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists