From: Andrew Morton <akpm@linux-foundation.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Robin Holt <holt@sgi.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [Patch] Convert max_user_watches to long.
Date: Wed, 27 Oct 2010 21:08:55 -0700 [thread overview]
Message-ID: <20101027210855.11c5a564.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1010271751090.12650@davide-lnx1>
On Wed, 27 Oct 2010 19:03:55 -0700 (PDT) Davide Libenzi <davidel@xmailserver.org> wrote:
> > Is the expected use case one-watch-per-user-per-fd? If so, then
> > perhaps the max number of user_watches should have some realtionship
> > with the max number of fds?
>
> Yes, the expected case is one watch per fd, but the reason the watch limit
> went in in the first place, was because of DoS potential of someone not
> playing nicely.
Sometimes DoS's are accidental. It only takes 25 people to be running
the same buggy (eg, slowly-leaky) app (or shared lib) at the same time...
There are surely plenty of ways of that sort of thing happening, of
course. Not that this fact actually improves anything.
next prev parent reply other threads:[~2010-10-28 4:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101027190914.146006767@gulag1.americas.sgi.com>
2010-10-27 19:09 ` [Patch] Convert max_user_watches to long Robin Holt
2010-10-27 19:31 ` Davide Libenzi
2010-10-27 23:45 ` Andrew Morton
2010-10-28 2:03 ` Davide Libenzi
2010-10-28 4:08 ` Andrew Morton [this message]
2010-10-01 20:01 max_user_watches overflows on 16TB system Robin Holt
2010-10-01 20:37 ` Davide Libenzi
2010-10-02 3:04 ` Eric W. Biederman
2010-10-02 14:04 ` Davide Libenzi
2010-10-04 19:44 ` [Patch] Convert max_user_watches to long Robin Holt
2010-10-06 2:21 ` Davide Libenzi
2010-10-09 7:50 ` Robin Holt
2010-10-10 19:05 ` Randy Dunlap
2010-10-11 4:49 ` Davide Libenzi
2010-10-14 17:15 ` Robin Holt
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=20101027210855.11c5a564.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=ebiederm@xmission.com \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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