'\" t
.\"     Title: __d_drop
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\"      Date: January 2017
.\"    Manual: The Linux VFS
.\"    Source: Kernel Hackers Manual 4.8.15
.\"  Language: English
.\"
.TH "__D_DROP" "9" "January 2017" "Kernel Hackers Manual 4\&.8\&." "The Linux VFS"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
__d_drop \- drop a dentry
.SH "SYNOPSIS"
.HP \w'void\ __d_drop('u
.BI "void __d_drop(struct\ dentry\ *\ " "dentry" ");"
.SH "ARGUMENTS"
.PP
\fIdentry\fR
.RS 4
dentry to drop
.RE
.SH "DESCRIPTION"
.PP
\fBd_drop\fR
unhashes the entry from the parent dentry hashes, so that it won\*(Aqt be found through a VFS lookup any more\&. Note that this is different from deleting the dentry \- d_delete will try to mark the dentry negative if possible, giving a successful _negative_ lookup, while d_drop will just make the cache lookup fail\&.
.PP
\fBd_drop\fR
is used mainly for stuff that wants to invalidate a dentry for some reason (NFS timeouts or autofs deletes)\&.
.PP
__d_drop requires dentry\->d_lock\&.
.SH "COPYRIGHT"
.br