From: "David Gómez" <david@pleyades.net>
To: Robert Love <rml@novell.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
John McCutchan <ttb@tentacle.dhs.org>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with inotify
Date: Sat, 2 Jul 2005 14:54:04 +0200 [thread overview]
Message-ID: <20050702125403.GA904@fargo> (raw)
In-Reply-To: <1120249515.6745.177.camel@betsy>
Hi Robert,
On Jul 01 at 04:25:15, Robert Love wrote:
> > either introduced by inotify or just made more likely (i.e. 100% of time)
> > by inotify but the change is elsewhere.
>
> The mount case is baffling. Inotify has no interaction whatsoever with
> mounting. Unmounting, definitely--see fs/inotify.c ::
> inotify_unmount_inodes().
Good news are that it seems unrelated to inotify. I updated to 2.6.13-rc1, and
tested it with and without the inotify patch. Now I get the mount process
hanged in inode_wait with the vanilla kernel, and working perfectly with the
patched one. Weird...
> [ Attached is the latest inotify, against 2.6.13-rc1. ]
I tested it with this patch.
bye
--
David Gómez Jabber ID: davidge@jabber.org
next prev parent reply other threads:[~2005-07-02 12:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 18:18 Problem with inotify David Gómez
2005-06-30 18:29 ` Robert Love
2005-06-30 18:38 ` David Gómez
2005-06-30 19:33 ` David Gómez
2005-06-30 20:39 ` Anton Altaparmakov
2005-06-30 20:48 ` David Gómez
2005-06-30 22:35 ` Anton Altaparmakov
2005-07-01 20:25 ` Robert Love
2005-07-02 12:54 ` David Gómez [this message]
2005-07-02 16:25 ` Robert Love
2005-07-02 9:12 ` Daniel Drake
2005-07-02 22:09 ` Anton Altaparmakov
2005-07-02 23:38 ` Daniel Drake
2005-07-03 0:08 ` Anton Altaparmakov
2005-07-03 10:34 ` Daniel Drake
2005-07-04 14:27 ` Anton Altaparmakov
2005-07-04 14:39 ` Anton Altaparmakov
2005-07-04 15:12 ` Anton Altaparmakov
2005-07-04 15:55 ` Gautam Singaraju
2005-07-04 16:00 ` Anton Altaparmakov
2005-07-04 17:57 ` Daniel Drake
2005-07-04 19:09 ` Anton Altaparmakov
2005-07-05 1:33 ` John McCutchan
2005-07-05 7:56 ` Anton Altaparmakov
2005-07-05 15:48 ` John McCutchan
2005-07-05 17:06 ` Anton Altaparmakov
2005-07-05 18:07 ` John McCutchan
2005-07-05 20:53 ` Anton Altaparmakov
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=20050702125403.GA904@fargo \
--to=david@pleyades.net \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--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 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.