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
| ||
|
Message-ID: <20091109134134.GB26965@oksana.dev.rtsoft.ru> Date: Mon, 9 Nov 2009 16:41:34 +0300 From: Anton Vorontsov <avorontsov@...mvista.com> To: David Miller <davem@...emloft.net> Cc: jdl@....com, linuxppc-dev@...abs.org, jason.wessel@...driver.com, afleming@...escale.com, netdev@...r.kernel.org, buytenh@...tstofly.org, shemminger@...tta.com Subject: Re: [PATCH RFC] gianfar: Do not call skb recycling with disabled IRQs On Sun, Nov 08, 2009 at 01:08:48AM -0800, David Miller wrote: > From: Anton Vorontsov <avorontsov@...mvista.com> > Date: Thu, 5 Nov 2009 19:57:38 +0300 > > > But that basically means that with skb recycling we can't safely > > use KGDBoE, though we can add something like this: > > Please stop adding special logic only to your driver to handle these > things. > > Either it's a non-issue, or it's going to potentially be an issue for > everyone using skb_recycle_check() in a NAPI driver, right? > > So why not add the "in_interrupt()" or whatever check to > skb_recycle_check() and if the context is unsuitable return false (0) > ok? I think the check is needed, yes. But if we add just that check, then we'll never do skb recycling in the tx path (since gianfar always grabs irqsave spinlock during tx ring cleanup, so the check will always return false). So we must add the check to keep polling with disabled IRQs safe, but we also should get rid of irqsave spinlock in the gianfar driver (to make the skb recycling actually work in most cases). Thanks! -- Anton Vorontsov email: cbouatmailru@...il.com irc://irc.freenode.net/bd2 -- 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
Powered by blists - more mailing lists