linux-kernel - Re: [PATCH 1/3] epoll: increase default max_user

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090128053819.GA10556@brong.net>
Date:	Wed, 28 Jan 2009 16:38:19 +1100
From:	Bron Gondwana <brong@...tmail.fm>
To:	Ray Lee <ray-lk@...rabbit.org>
Cc:	Davide Libenzi <davidel@...ilserver.org>,
	Bron Gondwana <brong@...tmail.fm>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 1/3] epoll: increase default max_user_instances to 1024

On Tue, Jan 27, 2009 at 08:07:32PM -0800, Ray Lee wrote:
> On Tue, Jan 27, 2009 at 8:00 PM, Davide Libenzi <davidel@...ilserver.org> wrote:
> > $ echo NN > /proc/sys/fs/epoll/max_user_instances
> >
> > Note that NN does not consume any resource "per se", so if you feel
> > threatened by such limit, you can go wild with it.
> 
> It's really simple. A kernel upgrade in a -stable series point release
> broke a rational user-space setup. If you don't want to adjust the
> defaults, then the sane thing to do is to revert the commit that
> caused the grief. Postfix is everywhere. Apache is everywhere.
> 
> Userspace is not broken here, and the whole idea of a -stable series
> is that administrators can upgrade to them without having to worry
> about things getting broken or making specific configuration changes
> by point release.

Oh man - it's java too:

http://pero.blogs.aprilmayjune.org/

they also suggest 1024, independantly of everyone else by the looks of
things.

   "A day and several installation routines later we figured out that
    the available epoll resources were not sufficient any more. Java JDK 1.6
    uses epoll to implement non-blocking-IO. With kernel 2.6.27 resource
    limits have been introduced and the default on openSuSE is 128 - way too
    low."

How many more people's wasted days is it going to take to convince you
that it's broken as currently implemented?

Bron.
--
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/