From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: <netdev@vger.kernel.org>, Glauber Costa <glommer@parallels.com>
Subject: Re: kernel panic, inconsistent lock, vanilla 3.3.4, 32bit, tcp
Date: Sun, 29 Apr 2012 11:00:16 +0300 [thread overview]
Message-ID: <6e1a75b751372f0ca5a58c2d0122a3cc@visp.net.lb> (raw)
In-Reply-To: <1335684762.2900.69.camel@edumazet-glaptop>
On 2012-04-29 10:32, Eric Dumazet wrote:
> On Sun, 2012-04-29 at 00:45 +0300, Denys Fedoryshchenko wrote:
>> Hi
>>
>> Just got repeatable kernel panic on loaded proxy server
>>
>> Here is the log:
>>
>> ---
>> Denys Fedoryshchenko
>
> Seems to be related to Glauber Costa work
>
> sk_memory_allocated_add() seems to assume __percpu_counter_add() is
> irq
> safe (truth is : it is not safe)
Not sure if it is related, but at my case, CONFIG_CGROUPS is not set
next prev parent reply other threads:[~2012-04-29 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 21:45 kernel panic, inconsistent lock, vanilla 3.3.4, 32bit, tcp Denys Fedoryshchenko
2012-04-29 7:32 ` Eric Dumazet
2012-04-29 7:45 ` Denys Fedoryshchenko
2012-04-29 8:00 ` Denys Fedoryshchenko [this message]
2012-04-29 8:17 ` Eric Dumazet
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=6e1a75b751372f0ca5a58c2d0122a3cc@visp.net.lb \
--to=denys@visp.net.lb \
--cc=eric.dumazet@gmail.com \
--cc=glommer@parallels.com \
--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).