-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Fix buffer overrun in bootstrap and (test-only) symlink_junction #109960
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
Can we switch to using docs.rs/junction instead? it makes me nervous to have all this unsafe code without tests ... |
For bootstrap that seems reasonable, done. For std I'm less sure. Even if we can (not really sure -- for a dev-dep I think we don't need it to use special rustc-dep-of-std stuff? Although maybe it would need to be in integration tests to avoid that...), deps in std (even dev-deps) have a way of causing headaches -- I'll leave it up to the reviewer. |
r=me on the bootstrap changes |
I'll look at these changes in a bit but I'm definitely in favour of avoiding headaches 🙂. I think the ultimate solution is for me to finally write an ACP (which I'll do now before I forget), fix up the std function with tests and finally get it stabilized. |
Ok this looks like an improvement, even if it's only avoiding an unlikely edge case. The new dependency looks fine for bootstrap though hopefully we can unify this code in a future libstd. @bors r+ |
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#109806 (Workaround rust-lang#109797 on windows-gnu) - rust-lang#109957 (diagnostics: account for self type when looking for source of unsolved type variable) - rust-lang#109960 (Fix buffer overrun in bootstrap and (test-only) symlink_junction) - rust-lang#110013 (Label `non_exhaustive` attribute on privacy errors from non-local items) - rust-lang#110016 (Run collapsed GUI test in mobile mode as well) - rust-lang#110022 (fix: fix regression in rust-lang#109203) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
bootstrap: drop some windows features They became unused after rust-lang#109960
bootstrap: drop some windows features They became unused after rust-lang#109960
bootstrap: drop some windows features They became unused after rust-lang#109960
bootstrap: drop some windows features They became unused after rust-lang/rust#109960
I don't think these can be hit in practice, due to their inputs being valid paths. It's also not security-sensitive code, but just... bad vibes.
I think this is still not really the right way to do this (in terms of path correctness), but is no worse than it was.
r? @ChrisDenton