From: Alessandro Zummo <a.zummo@towertech.it>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Dave Jones <davej@redhat.com>,
rtc-linux@googlegroups.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: rtc: INFO: possible circular locking dependency detected
Date: Tue, 28 Feb 2012 12:26:52 +0100 [thread overview]
Message-ID: <20120228122652.66cd9802@linux.lan.towertech.it> (raw)
In-Reply-To: <1330381713.5633.12.camel@lappy>
On Tue, 28 Feb 2012 00:28:33 +0200
Sasha Levin <sasha.levin@oracle.com> wrote:
> Hi all,
>
> I've stumbled on the following lockdep warning when running trinity under the KVM tool.
>
> (Is it the case of missing rtc->ops_lock in rtc_device_unregister?)
Hi,
the last time I checked we had a lock in rtc_device_unregister . I'll
give it a look.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2012-02-28 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 22:28 rtc: INFO: possible circular locking dependency detected Sasha Levin
2012-02-28 11:26 ` Alessandro Zummo [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-28 9:22 Sasha Levin
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=20120228122652.66cd9802@linux.lan.towertech.it \
--to=a.zummo@towertech.it \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sasha.levin@oracle.com \
/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