From: David Miller <davem@davemloft.net>
To: dingtianhong@huawei.com
Cc: edumazet@google.com, kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH] ifb: fix rcu_sched self-detected stalls
Date: Wed, 10 Jul 2013 18:44:35 -0700 (PDT) [thread overview]
Message-ID: <20130710.184435.1686234758615260434.davem@davemloft.net> (raw)
In-Reply-To: <51DCDD32.30102@huawei.com>
From: Ding Tianhong <dingtianhong@huawei.com>
Date: Wed, 10 Jul 2013 12:04:02 +0800
> According to the commit 16b0dc29c1af9df341428f4c49ada4f626258082
> (dummy: fix rcu_sched self-detected stalls)
>
> Eric Dumazet fix the problem in dummy, but the ifb will occur the
> same problem like the dummy modules.
>
> Trying to "modprobe ifb numifbs=30000" triggers :
>
> INFO: rcu_sched self-detected stall on CPU
>
> After this splat, RTNL is locked and reboot is needed.
>
> We must call cond_resched() to avoid this, even holding RTNL.
>
> Signed-off-by: Ding Tianhong <dingtianhong@huawei.com>
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2013-07-11 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 4:04 [PATCH] ifb: fix rcu_sched self-detected stalls Ding Tianhong
2013-07-11 1:44 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130710.184435.1686234758615260434.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=edumazet@google.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).