diff options
| author | Tetsuo Handa <[email protected]> | 2016-11-14 20:11:52 +0900 |
|---|---|---|
| committer | John Johansen <[email protected]> | 2017-01-15 13:41:09 -0800 |
| commit | a7f6c1b63b863d29f126d9b163ad5b40008544b2 (patch) | |
| tree | 0d6d855aafdd750417ce67c5ca9c490fe9ce7056 /tools/perf/scripts/python/bin | |
| parent | b8aa8453918ebfd93d78de56c2afd4b735e02e27 (diff) | |
AppArmor: Use GFP_KERNEL for __aa_kvmalloc().
Calling kmalloc(GFP_NOIO) with order == PAGE_ALLOC_COSTLY_ORDER is not
recommended because it might fall into infinite retry loop without
invoking the OOM killer.
Since aa_dfa_unpack() is the only caller of kvzalloc() and
aa_dfa_unpack() which is calling kvzalloc() via unpack_table() is
doing kzalloc(GFP_KERNEL), it is safe to use GFP_KERNEL from
__aa_kvmalloc().
Since aa_simple_write_to_buffer() is the only caller of kvmalloc()
and aa_simple_write_to_buffer() is calling copy_from_user() which
is GFP_KERNEL context (see memdup_user_nul()), it is safe to use
GFP_KERNEL from __aa_kvmalloc().
Therefore, replace GFP_NOIO with GFP_KERNEL. Also, since we have
vmalloc() fallback, add __GFP_NORETRY so that we don't invoke the OOM
killer by kmalloc(GFP_KERNEL) with order == PAGE_ALLOC_COSTLY_ORDER.
Signed-off-by: Tetsuo Handa <[email protected]>
Signed-off-by: John Johansen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions