Skip to content
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

Yank all 0.7 versions older than 0.7.6 #1412

Closed
faern opened this issue Dec 1, 2020 · 1 comment
Closed

Yank all 0.7 versions older than 0.7.6 #1412

faern opened this issue Dec 1, 2020 · 1 comment

Comments

@faern
Copy link
Contributor

faern commented Dec 1, 2020

Due to #1388. If the standard library ever do change the memory layout of SocketAddr, usage of this crate of versions before 0.7.6 will have undefined behaviour and lead to segfaults. And even if the standard library never do change the layout of those types, those older versions of this crate still makes assumptions they should not.

This is exactly what yanking is for. Marking a release as "should not be used". I think all versions of mio from 0.7.0 through 0.7.5 should be yanked from crates.io.

Related issues on other crates having the same problem: deprecrated/net2-rs#107, rust-lang/socket2#139

@Thomasdezeeuw
Copy link
Collaborator

Yanked all v0.7.x versions expect v0.7.6: https://crates.io/crates/mio/versions. I'm leaving v0.6.x as the dependencies are at fault there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants