From: Matt Mackall <mpm@selenic.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: netpoll trapped question
Date: Tue, 7 Sep 2004 12:22:12 -0500 [thread overview]
Message-ID: <20040907172212.GZ31237@waste.org> (raw)
In-Reply-To: <16701.60264.560942.236743@segfault.boston.redhat.com>
On Tue, Sep 07, 2004 at 01:10:00PM -0400, Jeff Moyer wrote:
> ==> Regarding Re: netpoll trapped question; Matt Mackall <mpm@selenic.com> adds:
>
> mpm> On Tue, Sep 07, 2004 at 12:53:17PM -0400, Jeff Moyer wrote: A random
> mpm> lock private to a given driver, for instance one taken on entry to the
> mpm> IRQ handler. If said driver tries to do a printk inside that lock and
> mpm> we recursively call the handler in netconsole, we're in trouble.
> mpm> These are the issues that will have to be cleaned up in individual
> mpm> drivers. So far, I haven't seen any reports, but I'm pretty sure such
> mpm> cases exist. I suppose it's also possible for us to disable recursion
> mpm> in netconsole instead of at the netpoll level.
> >> Recursion in netconsole is protected by the console semaphore.
>
> mpm> Yes, true. But we're still in trouble if we have nic irq handler ->
> mpm> take private lock -> printk -> netconsole -> nic irq handler -> take
> mpm> private lock. See?
>
> Okay, so that one has to be addressed on a per-driver basis. There's no
> way for us to detect that situation. And how do drivers address this?
> Simply don't printk inside the lock? I think that's reasonable.
That or drop the lock where possible.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-09-07 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 17:10 netpoll trapped question Jeff Moyer
2004-09-06 21:35 ` Matt Mackall
2004-09-07 16:33 ` Jeff Moyer
2004-09-07 16:50 ` Matt Mackall
2004-09-07 16:53 ` Jeff Moyer
2004-09-07 16:59 ` Matt Mackall
2004-09-07 17:10 ` Jeff Moyer
2004-09-07 17:22 ` Matt Mackall [this message]
2004-09-08 8:22 ` Herbert Xu
2004-09-08 8:34 ` Herbert Xu
2004-09-08 11:54 ` Jeff Moyer
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=20040907172212.GZ31237@waste.org \
--to=mpm@selenic.com \
--cc=jmoyer@redhat.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