From: Lee Revell <rlrevell@joe-job.com>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Robert Love <rml@novell.com>
Subject: Re: inotify bug?
Date: Thu, 15 Sep 2005 21:30:40 -0400 [thread overview]
Message-ID: <1126834240.4986.17.camel@mindpipe> (raw)
In-Reply-To: <20050915214848.GJ7991@shell0.pdx.osdl.net>
On Thu, 2005-09-15 at 14:48 -0700, Chris Wright wrote:
> * Lee Revell (rlrevell@joe-job.com) wrote:
> > I got this in dmesg with 2.6.13-rc7-rt3 the other day. Maybe it's
> > useful. There were no visible effects.
> >
> > idr_remove called for id=1024 which is not allocated.
>
> This should already be fixed in 2.6.13.
>
> http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7c657f2f25d50c602df9291bc6242b98fc090759
>
Thanks, nice to see that my suspicion of an off by one error was right
(the 1024 was a dead giveaway).
BTW the rate of kernel development is just insane these days, even
compared to a year ago. It's quite encouraging. At this rate we're
going to leave the "competition" in the dust.
Lee
prev parent reply other threads:[~2005-09-16 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 20:12 inotify bug? Lee Revell
2005-09-15 21:48 ` Chris Wright
2005-09-16 1:30 ` Lee Revell [this message]
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=1126834240.4986.17.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=chrisw@osdl.org \
--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