linux-kernel - [PATCH 1/8] fsnotify: allow notification requests to not include private data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090811163000.8648.87614.stgit@paris.rdu.redhat.com>
Date:	Tue, 11 Aug 2009 12:30:01 -0400
From:	Eric Paris <eparis@...hat.com>
To:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	viro@...IV.linux.org.uk
Subject: [PATCH 1/8] fsnotify: allow notification requests to not include
	private data

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@...hat.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/