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-next>] [day] [month] [year] [list]
Date:	Mon, 05 Nov 2012 20:42:32 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	linux-kernel@...r.kernel.org
CC:	Evgeniy Polyakov <zbr@...emap.net>, netdev@...r.kernel.org
Subject: connector and netlink_broadcast (semop failed for cookie ...)

Hello,

I've recently enabled CONFIG_CONNECTOR in kernel 3.6.6 and now I've got 
the message "semop failed for cookie ..." when using cryptsetup (I've 
never got that error before).

A short search revealed the following discussion about ignoring errors 
from netlink_broadcast_filtered(): https://lkml.org/lkml/2011/8/19/60

connector doesn't use netlink_broadcast_filtered() directly but it 
returns netlink_broadcast() in cn_netlink_send() while 
netlink_broadcast() just is a wrapper around netlink_broadcast_filtered().

Could it be the case that cn_netlink_send() has to ignore the same 
return codes as done in kobject_uevent_env()? Or maybe the users of 
cn_netlink_send() have to ignore them?

Regards,

Alexander
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ