| created | 2022-03-13T19:59:26Z |
|---|---|
| begin | 2022-03-11T19:02:15Z |
| end | 2022-03-11T19:24:19Z |
| path | src/sys |
| commits | 1 |
| date | 2022-03-11T19:24:19Z | |||
|---|---|---|---|---|
| author | kettenis | |||
| files | src/sys/uvm/uvm_extern.h | log | diff | annotate |
| src/sys/uvm/uvm_glue.c | log | diff | annotate | |
| src/sys/uvm/uvm_io.c | log | diff | annotate | |
| src/sys/uvm/uvm_map.c | log | diff | annotate | |
| src/sys/uvm/uvm_map.h | log | diff | annotate | |
| message |
Hold a read lock on the map while copying out data during a sysctl(2) call to prevent another thread from unmapping the memory and triggering an assertion or even corrupting random physical memory pages. This fix is similar to the change in uvm_glue.c rev. 1.74. However in this case we need to be careful since some sysctl(2) calls look at the map of the current process. In those cases we must not attempt to lock the map again. ok mpi@ Should fix: Reported-by: [email protected] |
|||