From: Eric Paris <eparis@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@ZenIV.linux.org.uk
Subject: [PATCH 1/8] fsnotify: allow notification requests to not include private data
Date: Tue, 11 Aug 2009 12:30:01 -0400 [thread overview]
Message-ID: <20090811163000.8648.87614.stgit@paris.rdu.redhat.com> (raw)
fsnotify currently expects everything using the generic notification
infrastructure to want to send private data with the notification.
fanotify has no such requirement (like inotify does) so support that
as well.
Signed-off-by: Eric Paris <eparis@redhat.com>
---
fs/notify/notification.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/fs/notify/notification.c b/fs/notify/notification.c
index 96ffbd0..cdf203c 100644
--- a/fs/notify/notification.c
+++ b/fs/notify/notification.c
@@ -173,7 +173,8 @@ int fsnotify_add_notify_event(struct fsnotify_group *group, struct fsnotify_even
struct fsnotify_event *last_event;
/* easy to tell if priv was attached to the event */
- INIT_LIST_HEAD(&priv->event_list);
+ if (priv)
+ INIT_LIST_HEAD(&priv->event_list);
/*
* There is one fsnotify_event_holder embedded inside each fsnotify_event.
next reply other threads:[~2009-08-11 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 16:30 Eric Paris [this message]
2009-08-11 16:30 ` [PATCH 2/8] fsnotify: provide the data type to should_send_event Eric Paris
2009-08-11 16:30 ` [PATCH 3/8] fsnotify: include data in should_send calls Eric Paris
2009-08-11 16:30 ` [PATCH 4/8] fsnotify: pass a file instead of an inode to open, read, and write Eric Paris
2009-08-11 16:30 ` [PATCH 5/8] fsnotify: send struct file when sending events to parents when possible Eric Paris
2009-08-11 16:30 ` [PATCH 6/8] fsnotify: per group notification queue merge types Eric Paris
2009-08-11 16:30 ` [PATCH 7/8] fsnotify: clone existing events Eric Paris
2009-08-11 16:30 ` [PATCH 8/8] fsnotify: replace an event on a list Eric Paris
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=20090811163000.8648.87614.stgit@paris.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).