From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: herbert@gondor.apana.org.au, mpm@selenic.com,
netdev@vger.kernel.org, mcarlson@broadcom.com
Subject: Re: netpoll + xmit_lock == deadlock
Date: Mon, 03 Aug 2009 12:15:12 -0700 (PDT) [thread overview]
Message-ID: <20090803.121512.75779533.davem@davemloft.net> (raw)
In-Reply-To: <1249301157.2893.11.camel@achroite>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Mon, 03 Aug 2009 13:05:57 +0100
> On Sun, 2009-08-02 at 13:07 -0700, David Miller wrote:
>> My position has always been that such printk's are simply
>> not allowed. (check archives if you don't believe me :-)
>>
>> The locking is going to get rediculious if we start having
>> to account for this.
>
> I agree with that, but this does seem quite restrictive. How can we be
> sure that none of the kernel functions used by a driver's TX path (e.g.
> kmalloc or DMA-mapping) will print debug or warning messages? If such
> guarantees exist, they do not seem to be documented.
Indeed, that's a good counter-argument.
Ho hum... so someone show me how ugly the locking is going
to get :-)
next prev parent reply other threads:[~2009-08-03 19:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 7:35 netpoll + xmit_lock == deadlock Herbert Xu
2009-07-29 19:07 ` Matt Mackall
2009-07-29 19:43 ` Neil Horman
2009-07-29 21:48 ` Matt Mackall
2009-07-29 23:15 ` Neil Horman
2009-07-29 23:17 ` Herbert Xu
2009-07-30 1:02 ` Neil Horman
2009-07-31 1:27 ` Herbert Xu
2009-07-29 22:38 ` Herbert Xu
2009-07-30 1:06 ` Neil Horman
2009-07-31 1:30 ` Herbert Xu
2009-07-31 12:56 ` Neil Horman
2009-07-31 13:02 ` Herbert Xu
2009-07-31 18:09 ` Neil Horman
2009-08-02 20:07 ` David Miller
2009-08-03 12:05 ` Ben Hutchings
2009-08-03 19:15 ` David Miller [this message]
2009-08-03 19:59 ` Matt Mackall
2009-08-04 4:19 ` David Miller
2009-08-04 6:48 ` Herbert Xu
2009-08-04 0:15 ` Herbert Xu
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=20090803.121512.75779533.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=herbert@gondor.apana.org.au \
--cc=mcarlson@broadcom.com \
--cc=mpm@selenic.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).