diff options
| author | David Hildenbrand <[email protected]> | 2016-03-08 12:30:46 +0100 |
|---|---|---|
| committer | Christian Borntraeger <[email protected]> | 2016-06-20 09:54:28 +0200 |
| commit | 0f7f84891516dc1ff7500fae12143710d2d9d11f (patch) | |
| tree | ae5185ba98c655404b8f5ee9e46060824fb08cba /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 998f637cc4b9ef3fa32b196294a3136ee05271a2 (diff) | |
s390/mm: fix races on gmap_shadow creation
Before any thread is allowed to use a gmap_shadow, it has to be fully
initialized. However, for invalidation to work properly, we have to
register the new gmap_shadow before we protect the parent gmap table.
Because locking is tricky, and we have to avoid duplicate gmaps, let's
introduce an initialized field, that signalizes other threads if that
gmap_shadow can already be used or if they have to retry.
Let's properly return errors using ERR_PTR() instead of simply returning
NULL, so a caller can properly react on the error.
Acked-by: Martin Schwidefsky <[email protected]>
Signed-off-by: David Hildenbrand <[email protected]>
Signed-off-by: Christian Borntraeger <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions