From: Jiri Kosina <jikos@kernel.org>
To: ksummit-discuss@lists.linux-foundation.org
Subject: [Ksummit-discuss] [CORE TOPIC] How to cope with 'creative' userspace
Date: Sat, 9 Jul 2016 00:35:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1607082043340.24757@cbobk.fhfr.pm> (raw)
There are many cases where certain components of modern linux desktops
slightly misuse the features provided by the kernel.
One of the latests instances was PIDs controller being instructed by an
init system to actually limit the number of created sub-processess/threads
to insanely small number
https://github.com/systemd/systemd/blob/dd050decb6ad131ebdeabb71c4f9ecb4733269c0/NEWS#L60
That of course caused horrible user experience left and right.
This is not a single and only exceptional instance of such issue.
I know that this in principle shouldn't really be directly our business,
but I believe we should be at least a bit nervous when our interfaces are
being used "incorrectly".
I dont' have a good idea from top of my head what we could immediately do
to improve this. Some sort of documented guidance on sane values for
certain userspace toggles? Issue a warning when we think userspace is
trying to shoot itself in a foot? ...?
Thanks,
--
Jiri Kosina
SUSE Labs
next reply other threads:[~2016-07-08 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 22:35 Jiri Kosina [this message]
2016-07-09 12:18 ` Vlastimil Babka
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=alpine.LNX.2.00.1607082043340.24757@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=ksummit-discuss@lists.linux-foundation.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