From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2] tools/xenconsoled: Increase file descriptor limit
Date: Tue, 17 Feb 2015 17:31:19 +0000 [thread overview]
Message-ID: <54E37AE7.7080409@citrix.com> (raw)
In-Reply-To: <20150217164811.GI2159@zion.uk.xensource.com>
On 17/02/15 16:48, Wei Liu wrote:
> On Tue, Feb 17, 2015 at 04:37:08PM +0000, Andrew Cooper wrote:
>
>> I am not sure what an admin could usefully do with a logged failure
>> message here. Xenconsoled will most likely not function in an
>> environment where it is not sufficiently privileged to make this limit
>> adjustment (use of privcmd and /dev/ptmx).
>>
> Does xenconsoled requires CAP_SYS_RESOURCE to make use of privcmd and
> /dev/ptmx? If not, there is a case that your setrlimit fails
> while other parts can still be functional, right?
A slim chance, yes if someone has specifically been playing with
capabilities.
I still don't see how an error message would be useful. Even if the
call fails, the process still has the default number of file descriptors
and can function fine up until that limit. If errors were meaningful in
this case, the function wouldn't be void.
~Andrew
next prev parent reply other threads:[~2015-02-17 17:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 16:21 [PATCH v2] tools/xenconsoled: Increase file descriptor limit Andrew Cooper
2015-02-17 16:28 ` Wei Liu
2015-02-17 16:37 ` Andrew Cooper
2015-02-17 16:48 ` Wei Liu
2015-02-17 17:31 ` Andrew Cooper [this message]
2015-02-17 17:58 ` Wei Liu
2015-02-17 17:55 ` [PATCH v3] " Andrew Cooper
2015-02-17 22:41 ` Don Slutz
2015-02-19 11:04 ` Wei Liu
2015-02-19 16:30 ` Ian Jackson
2015-02-19 17:56 ` Andrew Cooper
2015-02-19 19:04 ` David Vrabel
2015-02-24 11:50 ` Andrew Cooper
2015-02-24 17:37 ` Ian Jackson
2015-02-19 16:25 ` Ian Campbell
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=54E37AE7.7080409@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.