diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-10-17 13:46:04 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-17 13:46:04 +0200 |
| commit | 10b580a1d12691850e2ed1fed42582602a9b97c2 (patch) | |
| tree | c08a343cc5fcc82ffda53e0b72590738fb33cd5c /src/libsyntax/parse/parser | |
| parent | 0059411cae22c26f110344271688f8760623fc38 (diff) | |
| parent | 93ae6924af65f38b4998199c0da5ad75acde4466 (diff) | |
| download | rust-10b580a1d12691850e2ed1fed42582602a9b97c2.tar.gz rust-10b580a1d12691850e2ed1fed42582602a9b97c2.zip | |
Rollup merge of #65316 - oconnor663:noninheritable, r=alexcrichton
make File::try_clone produce non-inheritable handles on Windows ~**NOT READY FOR REVIEW.** This PR is currently mainly to trigger CI so that I can see what happens. (Is there a better way to trigger CI?) I don't know whether this change makes sense yet.~ (Edit: @Mark-Simulacrum clarified that CI doesn't currently run on Windows.) --- File handles shouldn't be inheritable in general. `std::process::Command` takes care of making them inheritable when child processes are spawned, and the `CREATE_PROCESS_LOCK` protects against races in that section on Windows. But `File::try_clone` has been creating inheritable file descriptors outside of that lock, which could be leaking into other child processes unintentionally. See also https://github.com/rust-lang/rust/pull/31069#discussion_r334117665.
Diffstat (limited to 'src/libsyntax/parse/parser')
0 files changed, 0 insertions, 0 deletions