| commit | 7de0816f699553514016f52a76e26d1c2ae14034 | |
| author | Ilya Leoshkevich <iii@linux.ibm.com> | |
| Tue, 14 Feb 2023 14:08:26 +0000 (14 15:08 +0100) | ||
| committer | Richard Henderson <richard.henderson@linaro.org> | |
| Tue, 21 Feb 2023 18:44:13 +0000 (21 08:44 -1000) | ||
| tree | d45c3f118d0b5108b6227ca1f9a72fa24519cd52 | treesnapshot (tar.gz zip) |
| parent | 21a474c41d18eb56186e2022e8e081c2b6011bd3 | commitdiff |
linux-user: Always exit from exclusive state in fork_end()
fork()ed processes currently start with
current_cpu->in_exclusive_context set, which is, strictly speaking, not
correct, but does not cause problems (even assertion failures).
With one of the next patches, the code begins to rely on this value, so
fix it by always calling end_exclusive() in fork_end().
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Message-Id: <20230214140829.45392-2-iii@linux.ibm.com>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
fork()ed processes currently start with
current_cpu->in_exclusive_context set, which is, strictly speaking, not
correct, but does not cause problems (even assertion failures).
With one of the next patches, the code begins to rely on this value, so
fix it by always calling end_exclusive() in fork_end().
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Message-Id: <20230214140829.45392-2-iii@linux.ibm.com>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
| linux-user/main.c | diffblobblamehistory | |
| linux-user/syscall.c | diffblobblamehistory |