netdev - Re: [PATCH] drivers/net: use tasklet_kill in device remove/close process

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] [day] [month] [year] [list]

Message-Id: <20121103.151602.1818450049632367167.davem@davemloft.net>
Date:	Sat, 03 Nov 2012 15:16:02 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	xtfeng@...il.com
Cc:	linux-kernel@...r.kernel.org, dannyfeng@...cent.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH] drivers/net: use tasklet_kill in device remove/close
 process

From: Xiaotian Feng <xtfeng@...il.com>
Date: Wed, 31 Oct 2012 18:29:57 +0800

> Some driver uses tasklet_disable in device remove/close process,
> tasklet_disable will inc tasklet->count and return. If the tasklet
> is not handled yet because some softirq pressure, the tasklet will
> placed on the tasklet_vec, never have a chance to excute. This might
> lead to ksoftirqd heavy loaded, wakeup with pending_softirq, but
> tasklet is disabled. tasklet_kill should be used in this case.
> 
> Signed-off-by: Xiaotian Feng <dannyfeng@...cent.com>

Applied.
--
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