diff options
author | Daniel Forrest <[email protected]> | 2014-12-02 15:59:42 -0800 |
---|---|---|
committer | Linus Torvalds <[email protected]> | 2014-12-03 09:36:04 -0800 |
commit | c4ea95d7cd08d9ffd7fa75e6c5e0332d596dd11e (patch) | |
tree | 528a94f26b4e2bc1ca8652a6dfa9a34d746c4d4f /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 2022b4d18a491a578218ce7a4eca8666db895a73 (diff) |
mm: fix anon_vma_clone() error treatment
Andrew Morton noticed that the error return from anon_vma_clone() was
being dropped and replaced with -ENOMEM (which is not itself a bug
because the only error return value from anon_vma_clone() is -ENOMEM).
I did an audit of callers of anon_vma_clone() and discovered an actual
bug where the error return was being lost. In __split_vma(), between
Linux 3.11 and 3.12 the code was changed so the err variable is used
before the call to anon_vma_clone() and the default initial value of
-ENOMEM is overwritten. So a failure of anon_vma_clone() will return
success since err at this point is now zero.
Below is a patch which fixes this bug and also propagates the error
return value from anon_vma_clone() in all cases.
Fixes: ef0855d334e1 ("mm: mempolicy: turn vma_set_policy() into vma_dup_policy()")
Signed-off-by: Daniel Forrest <[email protected]>
Reviewed-by: Michal Hocko <[email protected]>
Cc: Konstantin Khlebnikov <[email protected]>
Cc: Andrea Arcangeli <[email protected]>
Cc: Rik van Riel <[email protected]>
Cc: Tim Hartrick <[email protected]>
Cc: Hugh Dickins <[email protected]>
Cc: Michel Lespinasse <[email protected]>
Cc: Vlastimil Babka <[email protected]>
Cc: <[email protected]> [3.12+]
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions