Messages in this thread |  | | Date | Tue, 2 Apr 2013 10:52:15 -0700 | | Subject | Re: ipc,sem: sysv semaphore scalability | | From | Linus Torvalds <> |
| |
On Tue, Apr 2, 2013 at 9:08 AM, Sasha Levin <sasha.levin@oracle.com> wrote: > > By just playing with the 'msgsz' parameter with MSG_COPY set.
Hmm. Looking closer, I suspect you're testing without commit 88b9e456b164 ("ipc: don't allocate a copy larger than max"). That should limit the size passed in to prepare_copy -> load_copy to msg_ctlmax.
Now, I think it's possibly still a good idea to limit bufsz to INT_MAX regardless, but as far as I can see that prepare_copy -> load_copy path is the only place that can get confused. Everybody else uses size_t (or "long" in the case of r_maxsize) as far as I can tell.
Linus
|  |