diff options
| author | Eric Paris <eparis@redhat.com> | 2011-04-28 15:55:52 -0400 |
|---|---|---|
| committer | Eric Paris <eparis@redhat.com> | 2011-04-28 16:12:54 -0400 |
| commit | bf69d41d198138e3c601e9a6645f4f1369aff7e0 (patch) | |
| tree | 6cd3c35430f616732caa0096bd7791b56c8bd3ab /security | |
| parent | 5d30b10bd68df007e7ae21e77d1e0ce184b53040 (diff) | |
| download | linux-bf69d41d198138e3c601e9a6645f4f1369aff7e0.tar.gz linux-bf69d41d198138e3c601e9a6645f4f1369aff7e0.tar.bz2 linux-bf69d41d198138e3c601e9a6645f4f1369aff7e0.zip | |
flex_arrays: allow zero length flex arrays
Just like kmalloc will allow one to allocate a 0 length segment of memory
flex arrays should do the same thing. It should bomb if you try to use
something, but it should at least allow the allocation.
This is needed because when SELinux switched to using flex_arrays in 2.6.38
the inability to allocate a 0 length array resulted in SELinux policy load
returning -ENOSPC when previously it worked.
Based-on-patch-by: Steffen Klassert <steffen.klassert@secunet.com>
Signed-off-by: Eric Paris <eparis@redhat.com>
Tested-by: Chris Richards <gizmo@giz-works.com>
Cc: stable@kernel.org [2.6.38+]
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions