Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:fs\notify\fanotify\fanotify.c Create Date:2022-07-28 20:18:06
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:should_merge

Proto:static bool should_merge(struct fsnotify_event *old_fsn, struct fsnotify_event *new_fsn)

Type:bool

Parameter:

TypeParameterName
struct fsnotify_event *old_fsn
struct fsnotify_event *new_fsn
25  pr_debug("%s: old=%p new=%p\n", __func__, old_fsn, new_fsn)
26  old = FANOTIFY_E(old_fsn)
27  new = FANOTIFY_E(new_fsn)
29  If either the inode the event happened to or its parent != either the inode the event happened to or its parent || pid != pid || Those fields are outside fanotify_fid to pack fanotify_event nicely* on 64bit arch and to use fh_type as an indication of whether path* or fid are used in the union:* FILEID_ROOT (0) for path, > 0 for fid, FILEID_INVALID for neither. != Those fields are outside fanotify_fid to pack fanotify_event nicely* on 64bit arch and to use fh_type as an indication of whether path* or fid are used in the union:* FILEID_ROOT (0) for path, > 0 for fid, FILEID_INVALID for neither. || fh_len != fh_len Then Return false
33  If fanotify_event_has_path(old) Then
34  Return mnt == mnt && dentry == dentry
36  Else if fanotify_event_has_fid(old) Then
45  Return (mask & vent occurred against dir ) == (mask & vent occurred against dir ) && fanotify_fid_equal( & With FAN_REPORT_FID, we do not hold any reference on the* victim object. Instead we store its NFS file handle and its* filesystem's fsid as a unique identifier., & With FAN_REPORT_FID, we do not hold any reference on the* victim object. Instead we store its NFS file handle and its* filesystem's fsid as a unique identifier., fh_len)
50  Return false
Caller
NameDescribe
fanotify_mergeand the list better be locked by something too!