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 epoll_create1. #384

Closed
wants to merge 5 commits into from
Closed

Add epoll_create1. #384

wants to merge 5 commits into from

Conversation

kubo39
Copy link
Contributor

@kubo39 kubo39 commented Jul 9, 2016

No description provided.

@@ -80,6 +88,13 @@ pub fn epoll_create() -> Result<RawFd> {
}

#[inline]
pub fn epoll_create1(flags: EpollFdFlag) -> Result<RawFd> {
let res = unsafe { ffi::epoll_create1(flags.bits() | EPOLL_CLOEXEC.bits) };
Copy link
Contributor

@alex-gulyas alex-gulyas Jul 9, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • The way you are setting the default flag is actually enforcing it, therefore making it impossible for someone to call epoll_create1 without the EPOLL_CLOEXEC flag.
  • I don't think that any of the flags should be turned on by default, especially not without documentation. (Principle of Least Surprise)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Rust's standard library close-on-exec flag is set by default.
I'm not sure why so, however, I think it's security reason.
Thugh, someone might be surpised when I force to using fcntl(fd, F_SETFD, !O_CLOEXEC) if he want.
Okay, I'll fix it.

@kubo39 kubo39 changed the title Add epoll_create1 and set EPOLL_CLOEXEC flag by default. Add epoll_create1. Jul 9, 2016
@@ -8,12 +8,20 @@ mod ffi {

extern {
pub fn epoll_create(size: c_int) -> c_int;
pub fn epoll_create1(flags: c_int) -> c_int;
pub fn epoll_ctl(epfd: c_int, op: c_int, fd: c_int, event: *const EpollEvent) -> c_int;
pub fn epoll_wait(epfd: c_int, events: *mut EpollEvent, max_events: c_int, timeout: c_int) -> c_int;
Copy link
Member

@posborne posborne Jul 10, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @kubo39 , although this is not directly related to your PR we have been moving to defining ffi constants entirely in libc and using those rather than defining our own (see CONVENTIONS.md). it looks like the existing constants are present but epoll_create1 is not. Can you please do the following:

  1. Open up a PR to libc adding epoll_create1
  2. Update epoll.rs to use the ffi definitions from libc.

Also, thanks for the change!

@fiveop
Copy link
Contributor

fiveop commented Jul 12, 2016

There is a new libc version with your changes. Now, you can amend the pull request to use the new libc version and your additions to it. After that, we can merge this pull request.

@posborne
Copy link
Member

@kubo39 Can you just rebase your commits on master rather than having the merge commit back into your branch? Other than that, looks good to me.

@fiveop
Copy link
Contributor

fiveop commented Jul 15, 2016

This will probably create a merge conflict, because of the libc version. Please use the existing form of the dependency targeting the git repository instead of a fixed version.

@kubo39
Copy link
Contributor Author

kubo39 commented Jul 22, 2016

I'm sorry for being late.

@posborne
Copy link
Member

@kubo39 I think we want to remove the extern functions from nix and just depend on them directly from libc.

pub fn epoll_ctl(epfd: c_int, op: c_int, fd: c_int, event: *const EpollEvent) -> c_int;
pub fn epoll_wait(epfd: c_int, events: *mut EpollEvent, max_events: c_int, timeout: c_int) -> c_int;
}
}

bitflags!(
flags EpollFdFlag: c_int {
const EPOLL_NONBLOCK = 0x800,
const EPOLL_CLOEXEC = 0x80000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These constants should also come out of libc if possible.

@fiveop fiveop mentioned this pull request Aug 31, 2016
@homu
Copy link
Contributor

homu commented Sep 9, 2016

☔ The latest upstream changes (presumably #423) made this pull request unmergeable. Please resolve the merge conflicts.

@kamalmarhubi
Copy link
Member

Work on this seems to be continuing in #410, so I'm closing this one. Thanks for starting on this @kubo39!

@kubo39 kubo39 deleted the add_epoll_create1-and-set-cloexec branch September 10, 2016 01:58
homu added a commit that referenced this pull request Sep 16, 2016
Add epoll_create1

In order to get @kubo39's PR #384 forward, I cleaned up the commit history a bit and added `EpollEvent` back.

Since this module is used by mio, maybe @carllerche could comment on these changes.
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

Successfully merging this pull request may close these issues.

6 participants