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
| ||
|
Date: Sat, 29 Nov 2014 09:54:29 +0100 From: Rafał Miłecki <zajec5@...il.com> To: nick <xerofoify@...il.com> Cc: Michael Büsch <m@...s.ch>, Stefano Brivio <stefano.brivio@...imi.it>, Network Development <netdev@...r.kernel.org>, "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, b43-dev <b43-dev@...ts.infradead.org> Subject: Re: [PATCH] drivers:net:wireless: Add mutex locking for function, b43_op_beacon_set_time in main.c On 29 November 2014 at 04:32, nick <xerofoify@...il.com> wrote: > I don't have hardware for this driver on me, so I didn't test it. However this seems to > be correct from my reading of the code around this function and other locking related > to this driver. So do you say it's not executed in an atomic? >From *early* look it seems b43_update_templates is called from b43_op_beacon_set_tim and b43_op_bss_info_changed, both or them are mac80211 callbacks. That also should be safe, however I didn't check if it may conflict with some in-kernel code (still, assuming it's not atomic code, which I don't know!). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists