Messages in this thread | | | Date | Sat, 18 Aug 2007 07:13:50 +0200 | From | Willy Tarreau <> | Subject | Re: Kernel 2.6.20: INFO: possible circular locking dependency detected |
| |
On Thu, Aug 16, 2007 at 09:23:48PM +0100, Alan Cox wrote: > 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.
Is there any known unmerged fix for this one ?
Willy
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |