-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 10 pull requests #96824
Rollup of 10 pull requests #96824
Conversation
It previously linked to the unstable const-mut-cast method instead of the `mut` counterpart for `as_ref`.
The security example shows that `env::current_exe` will return the path used when the program was started. This is not really surprising considering how hard links work: after `ln foo bar`, the two files are _equivalent_. It is _not_ the case that `bar` is a “link” to `foo`, nor is `foo` a link to `bar`. They are simply two names for the same underlying data. The security vulnerability linked to seems to be different: there an attacker would start a SUID binary from a directory under the control of the attacker. The binary would respawn itself by executing the program found at `/proc/self/exe` (which the attacker can control). This is a real problem. In my opinion, the example given here doesn’t really show the same problem, it just shows a misunderstanding of what hard links are. I looked through the history a bit and found that the example was introduced in rust-lang#33526. That PR actually has two commits, and the first (8478d48) explains the race condition at the root of the linked security vulnerability. The second commit proceeds to replace the explanation with the example we have today. This commit reverts most of the second commit from rust-lang#33526.
This happened because the `SYSROOT` variable was set for `x test`, but not `x build`. Set it consistently for both to avoid unnecessary rebuilds.
The feature was stabilized in rust-lang#93745
`run-pass` produces a JSON file when enabling save analysis.
…-ptr-as_ref, r=JohnTitor Link to correct `as_mut` in docs for `pointer::as_ref` It previously linked to the unstable const-mut-cast method instead of the `mut` counterpart for `as_ref`. Closes rust-lang#96327
Add aliases for std::fs::canonicalize The aliases are `realpath` and `GetFinalPathNameByHandle` which are explicitly mentioned in `canonicalize`'s documentation.
…k-Simulacrum Add regression test fixes rust-lang#69785 This issue seems to have been fixed in the meantime.
…ark-Simulacrum Remove hard links from `env::current_exe` security example The security example shows that `env::current_exe` will return the path used when the program was started. This is not really surprising considering how hard links work: after `ln foo bar`, the two files are _equivalent_. It is _not_ the case that `bar` is a “link” to `foo`, nor is `foo` a link to `bar`. They are simply two names for the same underlying data. The security vulnerability linked to seems to be different: there an attacker would start a SUID binary from a directory under the control of the attacker. The binary would respawn itself by executing the program found at `/proc/self/exe` (which the attacker can control). This is a real problem. In my opinion, the example given here doesn’t really show the same problem, it just shows a misunderstanding of what hard links are. I looked through the history a bit and found that the example was introduced in rust-lang#33526. That PR actually has two commits, and the first (rust-lang@8478d48) explains the race condition at the root of the linked security vulnerability. The second commit proceeds to replace the explanation with the example we have today. This commit reverts most of the second commit from rust-lang#33526.
…Simulacrum Add regression and bug tests this tracks the behaviour from rust-lang#96572 in our test suite
…k-Simulacrum Enable compiler-docs by default for `compiler`, `codegen`, and `tools` profiles I had this overridden locally for a while and realized just now it should probably just be a default.
…k-Simulacrum Don't constantly rebuild clippy on `x test src/tools/clippy`. This happened because the `SYSROOT` variable was set for `x test`, but not `x build`. Set it consistently for both to avoid unnecessary rebuilds. This is a very small step towards rust-lang#76495.
…m-active, r=joshtriplett Remove `adx_target_feature` feature from active features list The feature was stabilized in rust-lang#93745
…ysis, r=Mark-Simulacrum Make the test `check-pass` not to produce a JSON file `run-pass` produces a JSON file when enabling save analysis. The original ICE happened on `cargo check`, moreover **without** the `generic_const_exprs` feature, so `check-pass` should be enough.
…riddle Enforce quote rule for JS source code We mostly used double quotes but still had a weird mix. This eslint rule will now enforce it. r? `@notriddle`
@bors r+ rollup=never p=10 |
📌 Commit 20ade86 has been approved by |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry |
☀️ Test successful - checks-actions |
Finished benchmarking commit (e612ce9): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Successful merges:
as_mut
in docs forpointer::as_ref
#96336 (Link to correctas_mut
in docs forpointer::as_ref
)env::current_exe
security example #96671 (Remove hard links fromenv::current_exe
security example)compiler
,codegen
, andtools
profiles #96756 (Enable compiler-docs by default forcompiler
,codegen
, andtools
profiles)x test src/tools/clippy
. #96757 (Don't constantly rebuild clippy onx test src/tools/clippy
.)adx_target_feature
feature from active features list #96769 (Removeadx_target_feature
feature from active features list)check-pass
not to produce a JSON file #96777 (Make the testcheck-pass
not to produce a JSON file)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup