netdev - Re: [net-next PATCH] Remove mutex_trylock and associated WARN on failure.

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]

Date:	Sat, 14 Feb 2009 23:46:19 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	jeffrey.t.kirsher@...el.com
Cc:	netdev@...r.kernel.org, jeff@...zik.org, gospo@...hat.com,
	david.graham@...el.com
Subject: Re: [net-next PATCH] Remove mutex_trylock and associated WARN on
 failure.

From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Thu, 12 Feb 2009 01:53:10 -0800

> Single-thread access must be ensured for ICH8 NVM and PHY operations.
> This synchronization is provided by the nvm_mutex. To assist in
> understanding the contexts from which this code could be reached,
> a WARN was output if the mutex was not going to be immediately
> acquirable (if !mutex_trylock()). The code has now been optimized,
> and we have verified that the few remaining mutex contentions are
> reasonable and non-blocking, and it is time to remove the
> mutex_trylock() and WARN messages.
> 
> Signed-off-by: dave graham <david.graham@...el.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.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