From: Johannes Berg <johannes@sipsolutions.net>
To: george@mvista.com
Cc: Robert Love <rml@novell.com>,
John McCutchan <ttb@tentacle.dhs.org>,
jim.houston@ccur.com, 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 21:03:12 +0200 [thread overview]
Message-ID: <1124996592.19546.12.camel@localhost> (raw)
In-Reply-To: <430E13D8.8070005@mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On Thu, 2005-08-25 at 11:54 -0700, George Anzinger wrote:
> I think the best thing is to take idr into user space and emulate the
> problem usage.
Good plan, I guess. Do you think that's easy?
> To this end, from the log it appears that you _might_ be
> moving between 0, 1 and 2 entries increasing the number each time. It
> also appears that the failure happens here:
> add 1023
> add 1024
> find 1024 or is it the remove that fails? It also looks like 1024 got
> allocated twice. Am I reading the log correctly?
Remove 1024 fails, but add(please make it >1024) seems to return 1024,
and find(1024) also seems to fail. Well, remove() probably has to
find(), but I'm not really sure what inotify does (maybe find first, to
see if it's valid).
> So, is it correct to assume that the tree is empty save these two at
> this time? I am just trying to figure out what the test program needs
> to do.
Yes, but all the smaller ones have been in it at some point in time.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2005-08-25 19:03 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
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 [this message]
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=1124996592.19546.12.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=jim.houston@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reuben-lkml@reub.net \
--cc=rml@novell.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox