From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Authenticated <NWQ3MzhlY2QwZDAzODVhN@steudten.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.20: INFO: possible circular locking dependency detected
Date: Thu, 16 Aug 2007 21:23:48 +0100 [thread overview]
Message-ID: <20070816212348.0d260d06@the-village.bc.nu> (raw)
In-Reply-To: <46C48E73.8090309@steudten.com>
On Thu, 16 Aug 2007 19:50:43 +0200
Authenticated <NWQ3MzhlY2QwZDAzODVhN@steudten.com> wrote:
>
> =======================================================
> [ INFO: possible circular locking dependency detected ]
> 2.6.20-1.2948.self #1
> -------------------------------------------------------
> squid/4058 is trying to acquire lock:
> (tty_mutex){--..}, at: [<c019fb54>] print_warning+0x8b/0x12e
>
> but task is already holding lock:
> (&s->s_dquot.dqptr_sem){----}, at: [<c01a0802>] dquot_alloc_inode+0x34/0x10a
>
> which lock already depends on the new lock.
Yep - known 2.6.20 problem. Its very very unlikely to ever cause a real
problem however.
next prev parent reply other threads:[~2007-08-16 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 17:50 Kernel 2.6.20: INFO: possible circular locking dependency detected Authenticated
2007-08-16 20:23 ` Alan Cox [this message]
2007-08-18 5:13 ` Willy Tarreau
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=20070816212348.0d260d06@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=NWQ3MzhlY2QwZDAzODVhN@steudten.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