.\" 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 "SD_IOCTL" "" "06 October 2005" "" ""

.SH NAME
sd_ioctl \- process an ioctl
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int sd_ioctl  (struct inode * \fIinode\fB, struct file * \fIfilp\fB, unsigned int \fIcmd\fB, unsigned long \fIarg\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIinode\fB\fR
only i_rdev/i_bdev members may be used
.TP
\fB\fIfilp\fB\fR
only f_mode and f_flags may be used
.TP
\fB\fIcmd\fB\fR
ioctl command number
.TP
\fB\fIarg\fB\fR
this is third argument given to ioctl(2) system call.
Often contains a pointer.
.SH "DESCRIPTION"
.PP
Returns 0 if successful (some ioctls return postive numbers on
success as well). Returns a negated errno value in case of error.
.SH "NOTE"
.PP
most ioctls are forward onto the block subsystem or further
down in the scsi subsytem.