lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20101027210855.11c5a564.akpm@linux-foundation.org>
Date:	Wed, 27 Oct 2010 21:08:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Davide Libenzi <davidel@...ilserver.org>
Cc:	Robin Holt <holt@....com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: [Patch] Convert max_user_watches to long.

On Wed, 27 Oct 2010 19:03:55 -0700 (PDT) Davide Libenzi <davidel@...ilserver.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ