From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Burgess <aab@cichlid.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dnotify oddity in 2.4.19pre6aa1
Date: Fri, 3 May 2002 17:31:09 +1000 [thread overview]
Message-ID: <20020503173109.1afdbec1.sfr@canb.auug.org.au> (raw)
In-Reply-To: <200204231658.g3NGwE203196@athlon.cichlid.com>
Hi Andrew,
Sorry I have been a bit slow on this.
On Tue, 23 Apr 2002 09:58:14 -0700 Andrew Burgess <aab@cichlid.com> wrote:
>
> I am seeing something very strange with the dnotify feature in kernel
> 2.4.19pre6aa1. I'm developing a file copy daemon that makes backups of
> files as soon as they change so I run dnotify on every directory in my
> system (essentially). I based my program on the example in dnotify.txt
> in the Documentation directory.
So far, so good :-)
> I notice that after a while two things happen:
>
> 1) In my copyd process I start getting signals for directories that are
> not changing. Even stranger, I get signals for fd that I've never
> opened.
OK, this is weird, but I am looking into it.
> 2) Other processes, like sendmail, start exiting with the same signal
> (RTMIN+5). (I use +5 because I started seeing the problem with +0 and I
> took a wild guess that RTMIN+0 was being used for something else).
Does your copyd fork and exit after it has enabled the dnotify? Is it
still running when other processes start being killed?
> This does not seem to happen if I reboot and do not restart my copyd
> process.
>
> My system does cycle through process descriptors every few minutes (lots
> of short lived server processes) and sendmail also runs through pids
> rapidly.
>
> I'm wondering if something isn't being properly reset or cleared when a
> process exits so when the same process or fd data structure (or
> whatever) is reused inside the kernel the signals are still active
> somehow? This is a SMP Athlon, perhaps an SMP race?
That is a possibility, although I thought we had stomped on this bug.
> Do I need to configure something more in my kernel? I don't see any
> config options for realtime or rt or anything like that. And it does
> work fine after a reboot.
No, should be fine.
Can you send me a copy of your copyd (or the relevant subparts of it),
please?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next prev parent reply other threads:[~2002-05-03 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 16:58 Andrew Burgess
2002-05-03 7:31 ` Stephen Rothwell [this message]
2002-05-04 7:41 ` Kurt Wall
2002-05-03 7:32 ` Stephen Rothwell
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=20020503173109.1afdbec1.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=aab@cichlid.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®