From: Knut Petersen <Knut_Petersen@t-online.de>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: [BUG: 3.13.0-rc4] inconsistent lock state
Date: Wed, 18 Dec 2013 08:54:35 +0100 [thread overview]
Message-ID: <52B154BB.8040506@t-online.de> (raw)
In-Reply-To: <1387306781.19078.288.camel@edumazet-glaptop2.roam.corp.google.com>
On 17.12.2013 19:59, Eric Dumazet wrote:
> On Tue, 2013-12-17 at 19:13 +0100, Knut Petersen wrote:
>> Hi Linus / everybody!
>>
>> Booting openSuSE 13.1 with kernel 3.13.0-rc4 triggers the attached
>> warning.
>>
>> cu,
>> Knut
>>
>>
> Following patch should solve the issue.
>
> http://patchwork.ozlabs.org/patch/301382/
Indeed, it solves the problem.
cu,
Knut
next prev parent reply other threads:[~2013-12-18 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52B09446.7060809@t-online.de>
2013-12-17 18:59 ` [BUG: 3.13.0-rc4] inconsistent lock state Eric Dumazet
2013-12-18 7:54 ` Knut Petersen [this message]
2013-12-17 19:06 ` Linus Torvalds
2013-12-17 19:24 ` David Miller
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=52B154BB.8040506@t-online.de \
--to=knut_petersen@t-online.de \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).