Re: [PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-10-07 Thread Rafael Aquini
On Mon, Oct 06, 2014 at 08:32:42PM +0200, Manfred Spraul wrote: > a) > SysV can be abused to allocate locked kernel memory. For most systems, a > small limit doesn't make sense, see the discussion with regards to SHMMAX. > > Therefore: Increase the sysv sem limits so that all known applications

Re: [PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-10-07 Thread Rafael Aquini
On Mon, Oct 06, 2014 at 08:32:42PM +0200, Manfred Spraul wrote: a) SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits so that all known applications will

[PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-10-06 Thread Manfred Spraul
a) SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits so that all known applications will work with these defaults. b) With regards to the maximum supported:

[PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-10-06 Thread Manfred Spraul
a) SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits so that all known applications will work with these defaults. b) With regards to the maximum supported:

Re: [PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-08-15 Thread Rafael Aquini
On Tue, Aug 12, 2014 at 09:29:16AM +0200, Manfred Spraul wrote: > a) > SysV can be abused to allocate locked kernel memory. For most systems, a > small limit doesn't make sense, see the discussion with regards to SHMMAX. > > Therefore: Increase the sysv sem limits so that all known applications

Re: [PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-08-15 Thread Rafael Aquini
On Tue, Aug 12, 2014 at 09:29:16AM +0200, Manfred Spraul wrote: a) SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits so that all known applications will

[PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-08-12 Thread Manfred Spraul
a) SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits so that all known applications will work with these defaults. b) With regards to the maximum supported:

[PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-08-12 Thread Manfred Spraul
a) SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits so that all known applications will work with these defaults. b) With regards to the maximum supported:

[PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-05-29 Thread Manfred Spraul
SysV can be abused to allocated locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits to the maximum supported. With regards to the maximum supported: Some of the specified hard limits are not

[PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM

2014-05-29 Thread Manfred Spraul
SysV can be abused to allocated locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: Increase the sysv sem limits to the maximum supported. With regards to the maximum supported: Some of the specified hard limits are not