From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>,
David Herrmann <dh.herrmann@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Mack <daniel@zonque.org>
Cc: mtk.manpages@gmail.com, Arnd Bergmann <arnd@arndb.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Tom Gundersen <teg@jklm.no>, Jiri Kosina <jkosina@suse.cz>,
Andy Lutomirski <luto@amacapital.net>,
Linux API <linux-api@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Djalal Harouni <tixxdz@opendz.org>
Subject: Re: kdbus: add documentation
Date: Tue, 20 Jan 2015 09:09:58 +0100 [thread overview]
Message-ID: <54BE0D56.5090301@gmail.com> (raw)
In-Reply-To: <87vblwtxee.fsf@mid.deneb.enyo.de>
Daniel, David,
On 11/30/2014 06:23 PM, Florian Weimer wrote:
> * David Herrmann:
>
>> On Sun, Nov 30, 2014 at 10:02 AM, Florian Weimer <fw@deneb.enyo.de> wrote:
>>> * Greg Kroah-Hartman:
>>>
>>>> +7.4 Receiving messages
>
>>> What happens if this is not possible because the file descriptor limit
>>> of the processes would be exceeded? EMFILE, and the message will not
>>> be received?
>>
>> The message is returned without installing the FDs. This is signaled
>> by EMFILE, but a valid pool offset.
>
> Oh. This is really surprising, so it needs documentation. But it's
> probably better than the alternative (return EMFILE and leave the
> message stuck, so that you receive it immediately again—this behavior
> makes non-blocking accept rather difficult to use correctly).
So, was this point in the end explicitly documented? I not
obvious that it is documented in the revised kdbus.txt that
Greg K-H sent out 4 days ago.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2015-01-20 8:10 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 5:02 [PATCH v2 00/13] Add kdbus implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add documentation Greg Kroah-Hartman
2014-11-21 8:29 ` Harald Hoyer
2014-11-21 17:12 ` Andy Lutomirski
2014-11-24 20:16 ` David Herrmann
2014-11-24 20:57 ` Andy Lutomirski
2014-11-26 11:55 ` David Herrmann
2014-11-26 15:30 ` Andy Lutomirski
2014-11-26 15:39 ` Andy Lutomirski
2014-11-30 9:08 ` Florian Weimer
2014-11-30 17:12 ` David Herrmann
2014-11-30 17:22 ` Florian Weimer
2014-11-30 8:56 ` Florian Weimer
2014-11-30 17:17 ` David Herrmann
2014-11-30 9:02 ` Florian Weimer
2014-11-30 17:15 ` David Herrmann
2014-11-30 17:23 ` Florian Weimer
2015-01-20 8:09 ` Michael Kerrisk (man-pages) [this message]
2015-01-20 8:25 ` Daniel Mack
2015-01-20 12:54 ` Michael Kerrisk (man-pages)
2014-11-21 5:02 ` kdbus: add header file Greg Kroah-Hartman
2014-11-21 8:34 ` Harald Hoyer
2014-11-21 8:55 ` Daniel Mack
2014-11-21 5:02 ` kdbus: add driver skeleton, ioctl entry points and utility functions Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add connection pool implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add connection, queue handling and message validation code Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add node and filesystem implementation Greg Kroah-Hartman
2014-11-21 15:55 ` Sasha Levin
2014-11-21 16:13 ` David Herrmann
2014-11-21 16:56 ` Greg Kroah-Hartman
2014-11-21 17:03 ` Sasha Levin
2014-11-21 17:55 ` Greg Kroah-Hartman
2014-11-21 16:35 ` Andy Lutomirski
2014-11-21 16:41 ` Andy Lutomirski
2014-11-21 16:53 ` David Herrmann
2014-11-21 5:02 ` kdbus: add code to gather metadata Greg Kroah-Hartman
2014-11-21 19:50 ` Andy Lutomirski
2014-12-01 13:50 ` Daniel Mack
2014-12-01 14:46 ` Andy Lutomirski
2014-11-21 5:02 ` kdbus: add code for notifications and matches Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add code for buses, domains and endpoints Greg Kroah-Hartman
2014-11-21 8:14 ` Harald Hoyer
2014-11-21 8:39 ` Harald Hoyer
2014-11-21 5:02 ` kdbus: add name registry implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add policy database implementation Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add Makefile, Kconfig and MAINTAINERS entry Greg Kroah-Hartman
2014-11-21 5:02 ` kdbus: add selftests Greg Kroah-Hartman
2014-11-21 6:02 ` [PATCH v2 00/13] Add kdbus implementation Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2014-10-29 22:00 [PATCH 00/12] " Greg Kroah-Hartman
2014-10-29 22:00 ` kdbus: add documentation Greg Kroah-Hartman
2014-10-30 12:20 ` Peter Meerwald
2014-11-02 1:29 ` Greg Kroah-Hartman
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=54BE0D56.5090301@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=dh.herrmann@gmail.com \
--cc=ebiederm@xmission.com \
--cc=fw@deneb.enyo.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=teg@jklm.no \
--cc=tixxdz@opendz.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).