From: Amy Griffis <amy.griffis@hp.com>
To: Clem Taylor <clem.taylor@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: inotify_add_watch() returning ENOSPC in 2.6.24 [watch descriptor leak?]
Date: Wed, 6 Feb 2008 22:04:10 -0500 [thread overview]
Message-ID: <20080207030409.GA14880@fc.hp.com> (raw)
In-Reply-To: <ecb4efd10802061140g929e699y8d79f1317c30478d@mail.gmail.com>
Clem Taylor wrote: [Wed Feb 06 2008, 02:40:58PM EST]
> > Good bug report, thanks. That code was significantly altered in June 2006
> > and perhaps something broke.
>
> I also tested on a 2.6.20 x86 desktop machine. It took ~8k iterations
> to fail, which matched max_user_watches. Once the program fails, it
> will fail right away if it is re-run.
>
> > It's a bit hard to find people who work on inotify, I'm afraid. If you had
> > the time to come up with a script or program which demonstrates the bug,
> > that would be super-helpful?
>
> Attached is a simple example that shows off the problem. On a system
> with a problem, it will only run for about
> fs.inotify.max_user_watches iterations. If everything is working, it
> should run forever.
I'll take a look at this. Thanks for providing a reproducer.
Amy
next prev parent reply other threads:[~2008-02-07 3:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 1:49 inotify_add_watch() returning ENOSPC in 2.6.24 [watch descriptor leak?] Clem Taylor
2008-02-06 9:51 ` Andrew Morton
2008-02-06 19:40 ` Clem Taylor
2008-02-07 3:04 ` Amy Griffis [this message]
2008-02-07 18:54 ` Ulisses Furquim
2008-02-07 21:24 ` Clem Taylor
2008-02-07 21:44 ` Andrew Morton
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=20080207030409.GA14880@fc.hp.com \
--to=amy.griffis@hp.com \
--cc=akpm@linux-foundation.org \
--cc=clem.taylor@gmail.com \
--cc=linux-kernel@vger.kernel.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.