From: Robert Love <rml@novell.com>
To: John McCutchan <ttb@tentacle.dhs.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Reuben Farrelly <reuben-lkml@reub.net>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Inotify problem [was Re: 2.6.13-rc6-mm1]
Date: Thu, 25 Aug 2005 09:47:52 -0400 [thread overview]
Message-ID: <1124977672.32272.10.camel@phantasy> (raw)
In-Reply-To: <1124977253.5039.13.camel@vertex>
On Thu, 2005-08-25 at 09:40 -0400, John McCutchan wrote:
> I get that message a lot. I know I have said this before (and was wrong)
> but I think the idr layer is busted.
This time I think I agree with you. ;-)
Let's just pass zero for the "above" parameter in idr_get_new_above(),
which is I believe the behavior of the other interface, and see if the
1024-multiple problem goes away. We definitely did not have that
before.
If it does, and we don't have another solution, let's run with that for
2.6.13. I don't want this bug released.
Robert Love
next prev parent reply other threads:[~2005-08-25 13:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.h7s290f.i6qp37@ifi.uio.no>
[not found] ` <fa.e1uvbs1.l407h7@ifi.uio.no>
2005-08-25 10:07 ` Inotify problem [was Re: 2.6.13-rc6-mm1] Reuben Farrelly
2005-08-25 12:18 ` Johannes Berg
2005-08-25 13:40 ` John McCutchan
2005-08-25 13:47 ` Robert Love [this message]
2005-08-25 14:03 ` Johannes Berg
2005-08-25 14:06 ` John McCutchan
2005-08-25 14:13 ` Johannes Berg
2005-08-25 14:39 ` John McCutchan
2005-08-25 14:13 ` John McCutchan
2005-08-25 14:41 ` Johannes Berg
2005-08-25 15:16 ` John McCutchan
2005-08-25 13:50 ` Johannes Berg
2005-08-25 14:03 ` John McCutchan
2005-08-25 13:33 ` John McCutchan
2005-08-25 15:18 ` Robert Love
2005-08-25 18:54 ` George Anzinger
2005-08-25 19:03 ` Johannes Berg
2005-08-25 19:06 ` John McCutchan
2005-08-25 19:04 ` John McCutchan
2005-08-25 23:10 ` George Anzinger
2005-08-25 23:20 ` Johannes Berg
2005-08-26 17:03 Jim Houston
2005-08-26 17:52 ` John McCutchan
2005-08-26 17:56 ` Robert Love
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=1124977672.32272.10.camel@phantasy \
--to=rml@novell.com \
--cc=akpm@osdl.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reuben-lkml@reub.net \
--cc=ttb@tentacle.dhs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.