Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1399194

getting mysterious (to me) EINVAL from inotify_rm_watch

From Felix von Leitner <felix-linuxkernel@fefe.de>
Newsgroups linux.kernel
Subject getting mysterious (to me) EINVAL from inotify_rm_watch
Date 2016-05-11 16:40 +0200
Message-ID <rxDsT-1yk-45@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

I am trying to add inotify support to my tail implementation (for -F).
This is what happens:

  inotify_init()                          = 4
  inotify_add_watch(4, "/tmp/foo", IN_MODIFY) = 1
  inotify_rm_watch(4, 1)                  = -1 EINVAL (Invalid argument)
  inotify_add_watch(4, "/tmp/foo", IN_MODIFY) = 2

There is also some polling, some reading and some statting going on here, but
those are on other descriptors than 4 so they should not matter).

Can somebody explain the EINVAL I'm getting from inotify_rm_watch to me?

This is a stock kernel 4.5.0.

Thanks,

Felix

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

getting mysterious (to me) EINVAL from inotify_rm_watch Felix von Leitner <felix-linuxkernel@fefe.de> - 2016-05-11 16:40 +0200
  Re: getting mysterious (to me) EINVAL from inotify_rm_watch Peter Meerwald-Stadler <pmeerw@pmeerw.net> - 2016-05-11 16:50 +0200
    Re: getting mysterious (to me) EINVAL from inotify_rm_watch Felix von Leitner <felix-linuxkernel@fefe.de> - 2016-05-11 17:20 +0200
    Re: getting mysterious (to me) EINVAL from inotify_rm_watch Felix von Leitner <felix-linuxkernel@fefe.de> - 2016-05-11 17:40 +0200

csiph-web