From: Evgeniy Polyakov <zbr@ioremap.net>
To: Alexander Holler <holler@ahsoftware.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: connector and netlink_broadcast (semop failed for cookie ...)
Date: Tue, 6 Nov 2012 01:11:59 +0400 [thread overview]
Message-ID: <20121105211159.GA4894@ioremap.net> (raw)
In-Reply-To: <509816A8.70005@ahsoftware.de>
Hi
On Mon, Nov 05, 2012 at 08:42:32PM +0100, Alexander Holler (holler@ahsoftware.de) wrote:
> 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?
We just do not know what to do with that error.
Pretty much it means nothing can be done about it.
There is no recovery path, no collection and resend, since it may lead to dos.
Its like knowing that udp packet get lost, but you do not have enough
buffer space to save it and block. Actually there is no buffer at all.
Kind of missed interrupt.
--
Evgeniy Polyakov
prev parent reply other threads:[~2012-11-05 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 19:42 connector and netlink_broadcast (semop failed for cookie ...) Alexander Holler
2012-11-05 21:11 ` Evgeniy Polyakov [this message]
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=20121105211159.GA4894@ioremap.net \
--to=zbr@ioremap.net \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).