public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John McCutchan <ttb@tentacle.dhs.org>
To: Andrew Morton <akpm@osdl.org>, Robert Love <rml@novell.com>,
	linux-kernel@vger.kernel.org, jim.houston@ccur.com
Subject: idr_get_new_above not working?
Date: Mon, 15 Aug 2005 10:16:46 -0400	[thread overview]
Message-ID: <1124115406.7369.6.camel@vertex> (raw)

Hey,

Inotify is using idr_get_new_above to make sure that the next watch
descriptor is larger/different than any of the previous watch
descriptors. We keep track of the largest wd that we get out of
idr_get_new_above, and pass that to idr_get_new_above. I have noticed
though, that idr_get_new_above always returns the first available id.
This causes a serious problem for inotify, because user space will get a
IGNORE event for a wd K that might refer to the last holder of the K.

-- 
John McCutchan <ttb@tentacle.dhs.org>

             reply	other threads:[~2005-08-15 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 14:16 John McCutchan [this message]
2005-08-15 16:27 ` [patch] inotify: idr_get_new_above not working? Robert Love
2005-08-15 16:35   ` John McCutchan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1124115406.7369.6.camel@vertex \
    --to=ttb@tentacle.dhs.org \
    --cc=akpm@osdl.org \
    --cc=jim.houston@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox