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

Add renameat2 and change their flags' type to c_uint #2116

Merged
merged 1 commit into from Mar 17, 2021

Conversation

JohnTitor
Copy link
Member

@JohnTitor JohnTitor commented Mar 17, 2021

Taking over #1508. This changes the type of some flags but it should've been c_uint.

Closes #1508

Co-Authored-By: Jörg Thalheim <github@thalheim.io>
Co-Authored-By: Philipp Gesang <phg@phi-gamma.net>
@rust-highfive
Copy link

r? @Amanieu

(rust-highfive has picked a reviewer for you, use r? to override)

@Amanieu
Copy link
Member

Amanieu commented Mar 17, 2021

@bors r+

@bors
Copy link
Contributor

bors commented Mar 17, 2021

📌 Commit b90fda7 has been approved by Amanieu

@bors
Copy link
Contributor

bors commented Mar 17, 2021

⌛ Testing commit b90fda7 with merge e3dd608...

@bors
Copy link
Contributor

bors commented Mar 17, 2021

☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing e3dd608 to master...

@bors bors merged commit e3dd608 into rust-lang:master Mar 17, 2021
@JohnTitor JohnTitor deleted the renameat2 branch March 17, 2021 23:44
@bgilbert
Copy link

The type change causes a build failure for openat (tailhook/openat#35). Should this have gone through a deprecation period per the breaking change policy?

@phi-gamma
Copy link
Contributor

Thanks for merging this!

cgwalters added a commit to cgwalters/openat that referenced this pull request Mar 19, 2021
Workaround tailhook#35
AKA rust-lang/libc#2116

Unfortunately since we made this libc::c_int in our
public API, we can't easily change it right now.

Closes: tailhook#35
@JohnTitor
Copy link
Member Author

The type change causes a build failure for openat (tailhook/openat#35). Should this have gone through a deprecation period per the breaking change policy?

@bgilbert I'd consider it as bugfix since renameat2 needs c_uint as their flag and the initial definition (i.e. c_int) should be wrong in that context. But hmm is there any use of the flags as c_int?

@bgilbert
Copy link

Well, it can be a bugfix and still be a breaking change. 🙂 But meanwhile, openat has been updated with a workaround in tailhook/openat#36.

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

Successfully merging this pull request may close these issues.

None yet

6 participants