From: Ying Xue <ying.xue@windriver.com>
To: lkp@lists.01.org
Subject: Re: Fwd: [rhashtable] WARNING: CPU: 0 PID: 10 at kernel/locking/mutex.c:570 mutex_lock_nested()
Date: Tue, 13 Jan 2015 15:50:22 +0800 [thread overview]
Message-ID: <54B4CE3E.8020009@windriver.com> (raw)
In-Reply-To: <20150112124216.GA26570@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
On 01/12/2015 08:42 PM, Thomas Graf wrote:
> On 01/12/15 at 09:38am, Ying Xue wrote:
>> Hi Thomas,
>>
>> I am really unable to see where is wrong leading to below warning
>> complaints. Can you please help me check it?
>
> Not sure yet. It's not your patch that introduced the issue though.
> It merely exposed the affected code path.
>
> Just wondering, did you test with CONFIG_DEBUG_MUTEXES enabled?
>
>
After I enable above option, I don't find similar complaints during my
testing.
Regards,
Ying
WARNING: multiple messages have this Message-ID (diff)
From: Ying Xue <ying.xue@windriver.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: <linux-kernel@vger.kernel.org>, <lkp@01.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: Fwd: [rhashtable] WARNING: CPU: 0 PID: 10 at kernel/locking/mutex.c:570 mutex_lock_nested()
Date: Tue, 13 Jan 2015 15:50:22 +0800 [thread overview]
Message-ID: <54B4CE3E.8020009@windriver.com> (raw)
In-Reply-To: <20150112124216.GA26570@casper.infradead.org>
On 01/12/2015 08:42 PM, Thomas Graf wrote:
> On 01/12/15 at 09:38am, Ying Xue wrote:
>> Hi Thomas,
>>
>> I am really unable to see where is wrong leading to below warning
>> complaints. Can you please help me check it?
>
> Not sure yet. It's not your patch that introduced the issue though.
> It merely exposed the affected code path.
>
> Just wondering, did you test with CONFIG_DEBUG_MUTEXES enabled?
>
>
After I enable above option, I don't find similar complaints during my
testing.
Regards,
Ying
next prev parent reply other threads:[~2015-01-13 7:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 19:48 [rhashtable] WARNING: CPU: 0 PID: 10 at kernel/locking/mutex.c:570 mutex_lock_nested() Fengguang Wu
2015-01-10 19:48 ` Fengguang Wu
2015-01-12 1:38 ` Fwd: " Ying Xue
2015-01-12 1:38 ` Ying Xue
2015-01-12 12:42 ` Thomas Graf
2015-01-12 12:42 ` Thomas Graf
2015-01-13 7:50 ` Ying Xue [this message]
2015-01-13 7:50 ` Ying Xue
2015-01-13 8:41 ` Thomas Graf
2015-01-13 8:41 ` Thomas Graf
2015-01-13 19:14 ` Cong Wang
2015-01-13 19:14 ` Cong Wang
2015-01-13 19:28 ` Thomas Graf
2015-01-13 19:28 ` Thomas Graf
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=54B4CE3E.8020009@windriver.com \
--to=ying.xue@windriver.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.