Re: [PATCH 3/4] ipc/shm.c: check for integer overflow during shmget.

2014-04-22 Thread Michael Kerrisk (man-pages)
On 04/21/2014 04:26 PM, Manfred Spraul wrote: > SHMMAX is the upper limit for the size of a shared memory segment, > counted in bytes. The actual allocation is that size, rounded up to > the next full page. > Add a check that prevents the creation of segments where the > rounded up size causes an i

RE: [PATCH 3/4] ipc/shm.c: check for integer overflow during shmget.

2014-04-22 Thread Motohiro Kosaki
> > SHMMAX is the upper limit for the size of a shared memory segment, > > counted in bytes. The actual allocation is that size, rounded up to > > the next full page. > > Add a check that prevents the creation of segments where the rounded > > up size causes an integer overflow. > > > > Signed-off-

Re: [PATCH 3/4] ipc/shm.c: check for integer overflow during shmget.

2014-04-22 Thread Davidlohr Bueso
On Mon, 2014-04-21 at 16:26 +0200, Manfred Spraul wrote: > SHMMAX is the upper limit for the size of a shared memory segment, > counted in bytes. The actual allocation is that size, rounded up to > the next full page. > Add a check that prevents the creation of segments where the > rounded up size

[PATCH 3/4] ipc/shm.c: check for integer overflow during shmget.

2014-04-21 Thread Manfred Spraul
SHMMAX is the upper limit for the size of a shared memory segment, counted in bytes. The actual allocation is that size, rounded up to the next full page. Add a check that prevents the creation of segments where the rounded up size causes an integer overflow. Signed-off-by: Manfred Spraul --- ip

[PATCH 3/4] ipc/shm.c: check for integer overflow during shmget.

2014-04-19 Thread Manfred Spraul
SHMMAX is the upper limit of a shared memory segment, counted in bytes. The actual allocation is that size, rounded up to the next full page. Add a check that prevents the creation of segments where the rounded up size causes an integer overflow. Signed-off-by: Manfred Spraul --- ipc/shm.c | 3 +