From: Matt Mackall <mpm@selenic.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 2/3] netpoll: netconsole
Date: Wed, 10 Sep 2003 04:01:21 -0500 [thread overview]
Message-ID: <20030910090121.GH4489@waste.org> (raw)
In-Reply-To: <20030910082908.GE29485@wotan.suse.de>
On Wed, Sep 10, 2003 at 10:29:08AM +0200, Andi Kleen wrote:
> > No, haven't encountered it. Which lock are we talking about, specifically?
>
> The hardware register lock of the low level device drivers.
>
> It's a different lock for each driver.
I was afraid you were getting at something like that. I've been
developing this on UP and the drivers I've been playing with aren't
too chatty so nothing's shown up.
And no, I don't think there's much that can be done to fix it, short
of putting in deadlock avoidance of some sort or auditing drivers. We
run a risk of infinite recursion if we manage to avoid the deadlock
anyway.
My current plan is to hope that such printks are rare except in
network driver development, in which case using netconsole or kgdb-o-e
is asking for trouble anyway.
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-09-10 9:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030910074256.GD4489@waste.org.suse.lists.linux.kernel>
2003-09-10 8:11 ` [PATCH 2/3] netpoll: netconsole Andi Kleen
2003-09-10 8:24 ` Matt Mackall
2003-09-10 8:29 ` Andi Kleen
2003-09-10 9:01 ` Matt Mackall [this message]
2003-09-10 16:00 ` Mitchell Blank Jr
2003-09-12 5:33 ` Mitchell Blank Jr
2003-09-12 5:57 ` Matt Mackall
2003-09-12 19:40 ` Andrew Morton
2003-09-10 7:42 Matt Mackall
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=20030910090121.GH4489@waste.org \
--to=mpm@selenic.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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