summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2019-04-26 13:37:25 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2019-04-26 13:37:25 -0400
commit25b229dff4ffffd0fad2dd409faf1e2ae4d94866 (patch)
tree386d48b43faefef9e636e88641b5bdb4668da297 /kernel
parentf4ec3a3d43bcdcf6295af9f3715a5a33f59bb6ce (diff)
downloadlinux-stable-25b229dff4ffffd0fad2dd409faf1e2ae4d94866.tar.gz
linux-stable-25b229dff4ffffd0fad2dd409faf1e2ae4d94866.tar.bz2
linux-stable-25b229dff4ffffd0fad2dd409faf1e2ae4d94866.zip
fsnotify(): switch to passing const struct qstr * for file_name
Note that in fnsotify_move() and fsnotify_link() we are guaranteed that dentry->d_name won't change during the fsnotify() evaluation (by having the parent directory locked exclusive), so we don't need to fetch dentry->d_name.name in the callers. In fsnotify_dirent() the same stability of dentry->d_name is also true, but it's a bit more convoluted - there is one callchain (devpts_pty_new() -> fsnotify_create() -> fsnotify_dirent()) where the parent is _not_ locked, but on devpts ->d_name of everything is unchanging; it has neither explicit nor implicit renames. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions