linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: Knut_Petersen@t-online.de
Cc: linux-kernel@vger.kernel.org, paulus@samba.org,
	mostrows@earthlink.net, linux-ppp@vger.kernel.org
Subject: Re: [BUG] 2.6.38-rc2: Circular Locking Dependency
Date: Mon, 07 Feb 2011 07:28:56 +0000	[thread overview]
Message-ID: <20110206.232856.246531984.davem@davemloft.net> (raw)
In-Reply-To: <4D3D45A3.7040809@t-online.de>

From: Knut Petersen <Knut_Petersen@t-online.de>
Date: Mon, 24 Jan 2011 10:25:55 +0100

> As I was hunting something different I found the following (potential)
> problem on an openSuSE 11.3 system with kernel 2.6.38-rc2.
> The message is triggerd by smpppd starting a dsl connection.
> 
> Knut
> 
> 
>  NET: Registered protocol family 24
> 
>  ===========================>  [ INFO: possible circular locking dependency detected ]
>  2.6.38-rc2-kape #7
>  -------------------------------------------------------
>  pppd/2529 is trying to acquire lock:
>   (&(&pch->downl)->rlock){+.....}, at: [<f814a634>] ppp_push+0x59/0x4a8
> [ppp_generic]
> 
>  but task is already holding lock:
>   (&(&ppp->wlock)->rlock){+.-...}, at: [<f814ae1b>]
> ppp_xmit_process+0x19/0x451 [ppp_generic]
> 
>  which lock already depends on the new lock.

I've stared over this trace several times and can't figure out what
the problem is.

Paul, any idea?

  reply	other threads:[~2011-02-07  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24  9:25 [BUG] 2.6.38-rc2: Circular Locking Dependency Knut Petersen
2011-02-07  7:28 ` David Miller [this message]
2011-02-07 10:29   ` Paul Mackerras
2011-02-07 10:43     ` Paul Mackerras
2011-02-08  7:51       ` Knut Petersen
2011-02-08  8:07         ` David Miller
2011-02-08 23:04           ` David Miller
2011-02-09  7:26             ` Knut Petersen

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=20110206.232856.246531984.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Knut_Petersen@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=mostrows@earthlink.net \
    --cc=paulus@samba.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).