Lines Matching refs:parent
103 * parent cares. Thus when an event happens on a child it can quickly tell
104 * if there is a need to find a parent and send the event to the parent.
124 * d_flags to indicate parental interest (their parent is the
143 /* Are inode/sb/mount interested in parent and name info with this event? */
149 /* We only send parent/name to inode/sb/mount for events on non-dir */
155 * parent/name info to inode/sb/mount. Otherwise, a watching parent
160 /* Did either inode/sb/mount subscribe for events with parent/name? */
166 /* Did they subscribe for this event with parent/name info? */
171 * Notify this dentry's parent about a child's events with child name info
172 * if parent is watching or if inode/sb/mount are interested in events with
173 * parent and name info.
175 * Notify only the child without name info if parent is not watching and
176 * inode/sb/mount are not interested in events with parent and name info.
184 struct dentry *parent;
194 * Do inode/sb/mount care about parent and name info on non-dir?
201 parent = NULL;
206 /* Does parent inode care about events on children? */
207 parent = dget_parent(dentry);
208 p_inode = parent->d_inode;
214 * Include parent/name in notification either if some notification
215 * groups require parent info or the parent is interested in this event.
219 /* When notifying parent, child should be passed as data */
222 /* Notify both parent and child with child name info */
234 dput(parent);
283 * dnotify, where it means file was renamed within same parent.
304 * Some events can be sent on both parent dir and child marks
305 * (e.g. FS_ATTRIB). If both parent dir and child are
306 * watching, report the event once to parent dir with name (if