netdev - Re: [PATCH V2 2/2] ath6kl: replace semaphore with mutex

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: <87h9cliooi.fsf@kamboji.qca.qualcomm.com>
Date:	Wed, 22 Jun 2016 08:59:59 +0000
From:	"Valo, Kalle" <kvalo@....qualcomm.com>
To:	Chaehyun Lim <chaehyun.lim@...il.com>
CC:	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"ath6kl@...ts.infradead.org" <ath6kl@...ts.infradead.org>
Subject: Re: [PATCH V2 2/2] ath6kl: replace semaphore with mutex

(Adding ath6k list)

Chaehyun Lim <chaehyun.lim@...il.com> writes:

> It replaces struct semaphore sem with struct mutex mutex
>
> Reported-by: kbuild test robot <lkp@...el.com>
> Signed-off-by: Chaehyun Lim <chaehyun.lim@...il.com>
> ---
> V2: fix build failure reported by kbuild test robot

I don't think Reported-by is correct, it should be only used when
reporting the original issue

Have you tested this on a real device? I'm reluctant to apply this big
locking change without some level of testing.

-- 
Kalle Valo