From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Folkert van Heusden <folkert@vanheusden.com>
Subject: Re: 2.6.21.4: possible circular locking dependency detected
Date: Sun, 24 Jun 2007 17:35:11 +0200 [thread overview]
Message-ID: <467E8F2F.2090409@xs4all.nl> (raw)
In-Reply-To: <467ABCAD.7070304@xs4all.nl>
Udo van den Heuvel wrote:
> Udo van den Heuvel wrote:
>
>> While copying a small file over to a windows box via cifs, once again I
>> got something like this:
>
> Again with 2.6.21.5:
>
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 2.6.21.5 #10
> -------------------------------------------------------
(cut)
There is a bugzilla entry with some more info.
http://bugzilla.kernel.org/show_bug.cgi?id=8377
It looks like the bug has been there for a while. When will it go?
Networking (at least) is not reliable in my situation.
prev parent reply other threads:[~2007-06-24 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 17:45 2.6.21.4: possible circular locking dependency detected Udo van den Heuvel
2007-06-21 18:00 ` Udo van den Heuvel
2007-06-23 15:00 ` Udo van den Heuvel
2007-06-24 15:35 ` Udo van den Heuvel [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=467E8F2F.2090409@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@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).