From: Alexander Holler <holler@ahsoftware.de>
To: linux-kernel@vger.kernel.org
Cc: Evgeniy Polyakov <zbr@ioremap.net>, netdev@vger.kernel.org
Subject: connector and netlink_broadcast (semop failed for cookie ...)
Date: Mon, 05 Nov 2012 20:42:32 +0100 [thread overview]
Message-ID: <509816A8.70005@ahsoftware.de> (raw)
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
next reply other threads:[~2012-11-05 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 19:42 Alexander Holler [this message]
2012-11-05 21:11 ` connector and netlink_broadcast (semop failed for cookie ...) Evgeniy Polyakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=509816A8.70005@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zbr@ioremap.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.