From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Eric Paris <eparis@redhat.com>
Cc: Lino Sanfilippo <LinoSanfilippo@gmx.de>,
viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
vasily.novikov@kaspersky.com
Subject: Re: [PATCH] fs, fanotify: dont send notification event for coredump file
Date: Tue, 27 Mar 2012 00:27:00 +0200 [thread overview]
Message-ID: <20120326222700.GB2805@Neptun> (raw)
In-Reply-To: <1332781423.384.1.camel@localhost>
On Mon, Mar 26, 2012 at 01:03:43PM -0400, Eric Paris wrote:
> How does this work with something like abrt, which causes core files to
> be created in a known dir. It then watches (I have no idea if it uses
> *notify) for new core files and processes them when they appear. Would
> we be able to get any notification of core files with this patch? Maybe
> we need a way to just not allow ourselves to block on core files?
No we would not get notifications for core files with this patch any more.
I see that this is a drawback for applications that want to track those
files.
But unfortunately I dont see how we could tell if a core file is created by
a fanotify listener or not.
The easiest thing would probably be if we had two flags, one to suppress
"pure notification" events and one to suppress permission event.
For example if we had:
FMODE_NONOTIFY: suppress pure notification events
FMODE_NOPERMNOTIFY: suppress permission events
we would only use FMODE_NOPERMNOTIFY for core files then.
prev parent reply other threads:[~2012-03-26 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 1:28 [PATCH] fs, fanotify: dont send notification event for coredump file Lino Sanfilippo
2012-03-26 17:03 ` Eric Paris
2012-03-26 22:27 ` Lino Sanfilippo [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=20120326222700.GB2805@Neptun \
--to=linosanfilippo@gmx.de \
--cc=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=vasily.novikov@kaspersky.com \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).