Skip to content

Conversation

besser82
Copy link

No description provided.

@itdaniher
Copy link

would love to see this merged!

@Hello71
Copy link

Hello71 commented Jul 19, 2021

this patch is not correct. inotify_init is not the same as inotify_init1. this leaves whatever junk was previously in x0 as flags, which should always be 1 from PyArg_ParseTuple. kernel will return EINVAL if (flags&~(IN_NONBLOCK|IN_CLOEXEC)), and 1 is neither of those. therefore inotify will always fail. how did you test this?

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.

3 participants