| commit | 284b327be2f86cf751316ff344b6945e580e654f | |
| author | Pavel Emelyanov <xemul@openvz.org> | |
| Sun, 11 Nov 2007 06:08:30 +0000 (10 22:08 -0800) | ||
| committer | David S. Miller <davem@davemloft.net> | |
| Sun, 11 Nov 2007 06:08:30 +0000 (10 22:08 -0800) | ||
| tree | 61a5e5b353be80e092795e357863509861a6a774 | treesnapshot (tar.gz zip) |
| parent | 5c80f1ae9842a8b7985acd0f02efb9828effb05f | commitdiff |
[UNIX]: The unix_nr_socks limit can be exceeded
The unix_nr_socks value is limited with the 2 * get_max_files() value,
as seen from the unix_create1(). However, the check and the actual
increment are separated with the GFP_KERNEL allocation, so this limit
can be exceeded under a memory pressure - task may go to sleep freeing
the pages and some other task will be allowed to allocate a new sock
and so on and so forth.
So make the increment before the check (similar thing is done in the
sock_kmalloc) and go to kmalloc after this.
Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
The unix_nr_socks value is limited with the 2 * get_max_files() value,
as seen from the unix_create1(). However, the check and the actual
increment are separated with the GFP_KERNEL allocation, so this limit
can be exceeded under a memory pressure - task may go to sleep freeing
the pages and some other task will be allowed to allocate a new sock
and so on and so forth.
So make the increment before the check (similar thing is done in the
sock_kmalloc) and go to kmalloc after this.
Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
| net/unix/af_unix.c | diffblobblamehistory |