.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "ILOOKUP5_NOWAIT" "9" "09 October 2005" "" ""

.SH NAME
ilookup5_nowait \- search for an inode in the inode cache
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
struct inode * ilookup5_nowait  (struct super_block * \fIsb\fB, unsigned long \fIhashval\fB, int (*\fItest\fB)
struct inode *, void *, void * \fIdata\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIsb\fB\fR
super block of file system to search
.TP
\fB\fIhashval\fB\fR
hash value (usually inode number) to search for
.TP
\fB\fItest\fB\fR
callback used for comparisons between inodes
.TP
\fB\fIdata\fB\fR
opaque data pointer to pass to \fItest\fR
.SH "DESCRIPTION"
.PP
\fBilookup5\fR uses \fBifind\fR to search for the inode specified by \fIhashval\fR and
\fIdata\fR in the inode cache. This is a generalized version of \fBilookup\fR for
file systems where the inode number is not sufficient for unique
identification of an inode.
.PP
If the inode is in the cache, the inode is returned with an incremented
reference count.  Note, the inode lock is not waited upon so you have to be
very careful what you do with the returned inode.  You probably should be
using \fBilookup5\fR instead.
.PP
Otherwise NULL is returned.
.PP
Note, \fItest\fR is called with the inode_lock held, so can't sleep.