From: "Manfred Spraul" <manfred@colorfullife.com>
To: "Frank van Maarseveen" <F.vanMaarseveen@inter.NL.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: <=2.4.17 deadlock (RedHat 7.2, SMP, ext3 related?) (2)
Date: Mon, 24 Dec 2001 22:22:53 +0100 [thread overview]
Message-ID: <003301c18cc1$2aa7eeb0$010411ac@local> (raw)
In-Reply-To: <002101c18cb7$f575b3c0$010411ac@local> <20011224215615.A22826@iapetus.localdomain>
From: "Frank van Maarseveen" <F.vanMaarseveen@inter.NL.net>
>
> 0xc03fe0b1 <stext_lock+7289>: cmpb $0x0,0xc05dd400
> 0xc03fe0b8 <stext_lock+7296>: repz nop
> 0xc03fe0ba <stext_lock+7298>: jle 0xc03fe0b1 <stext_lock+7289>
> 0xc03fe0bc <stext_lock+7300>: jmp 0xc013fde0 <get_chrfops+240>
I assume 0xd05dd400 is kernel_flag.
> 0xc0403068 <stext_lock+27696>: cmpb $0x0,0xc057d540
> 0xc040306f <stext_lock+27703>: repz nop
> 0xc0403071 <stext_lock+27705>: jle 0xc0403068 <stext_lock+27696>
> 0xc0403073 <stext_lock+27707>: jmp 0xc0292df0 <ppp_destroy_interface+68>
And 0xc057d540 is all_ppp_lock.
The only obvious abuse is that both ppp_destroy_interface and ppp_create_interface
call rtnl_lock (that's a semaphore) with the spinlock acquired.
--
Manfred
next prev parent reply other threads:[~2001-12-24 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-24 20:17 <=2.4.17 deadlock (RedHat 7.2, SMP, ext3 related?) (2) Manfred Spraul
2001-12-24 20:56 ` Frank van Maarseveen
2001-12-24 21:22 ` Manfred Spraul [this message]
[not found] ` <005c01c18cc3$305283f0$010411ac@local>
2001-12-25 12:42 ` Frank van Maarseveen
-- strict thread matches above, loose matches on Subject: below --
2001-12-23 22:53 <=2.4.17 deadlock (RedHat 7.2, SMP) Frank van Maarseveen
2001-12-24 19:48 ` <=2.4.17 deadlock (RedHat 7.2, SMP, ext3 related?) (2) Frank van Maarseveen
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='003301c18cc1$2aa7eeb0$010411ac@local' \
--to=manfred@colorfullife.com \
--cc=F.vanMaarseveen@inter.NL.net \
--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