From: John <jhnlmn@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: eparis@redhat.com
Subject: What is the status of fanotify bugs?
Date: Sun, 17 Jun 2012 21:02:50 -0700 (PDT) [thread overview]
Message-ID: <1339992170.35835.YahooMailClassic@web113213.mail.gq1.yahoo.com> (raw)
Hi,
I googled and found at least 2 fanotify bugs,
which were discussed and patches were submitted but never merged into the kernel:
1. This one is more than 2 years old. Seems to be an obvious bug:
http://groups.google.com/group/linux.kernel/browse_thread/thread/46b25f4dfc96d811
2. This discussion was abruptly terminated last year:
http://groups.google.com/group/linux.kernel/browse_thread/thread/5e21ff2b0c446b69
And I have another problem, which is a complete show stopper for me:
fsnotify/fanotify do not pass file/directory creation/deletion events
when working in FAN_MARK_MOUNT mode.
I was hoping to get notified about file system changes, but it appears to be impossible.
A directory with many subdirectories can be deleted and fsnotify/fanotify completely ignore this event.
So, I wonder whether fsnotify/fanotify framework is still being maintained and used by anybody.
If nobody else cares about it, then I will need to make my own file system notification hook.
But, of course, it would be better to fix fsnotify/fanotify so that I can avoid maintaining my own notification code.
What do you think?
Thank you
John
next reply other threads:[~2012-06-18 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 4:02 John [this message]
2012-06-18 10:08 ` What is the status of fanotify bugs? (ENOMAINTAINER ?) Alan Cox
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=1339992170.35835.YahooMailClassic@web113213.mail.gq1.yahoo.com \
--to=jhnlmn@yahoo.com \
--cc=eparis@redhat.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®