netdev - Re: netpoll + xmit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090803.121512.75779533.davem@davemloft.net>
Date:	Mon, 03 Aug 2009 12:15:12 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	herbert@...dor.apana.org.au, mpm@...enic.com,
	netdev@...r.kernel.org, mcarlson@...adcom.com
Subject: Re: netpoll + xmit_lock == deadlock

From: Ben Hutchings <bhutchings@...arflare.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 :-)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html