linux-mips
[Top] [All Lists]

Re: [Iscsitarget-devel] mips kernel 2.6.16rc1 + IET 0.4.13 - /dev/ietct

To: Frederic Temporelli <frederic.temporelli@tele2.fr>
Subject: Re: [Iscsitarget-devel] mips kernel 2.6.16rc1 + IET 0.4.13 - /dev/ietctl - ioctl unknown command
From: Ming Zhang <mingz@ele.uri.edu>
Date: Wed, 08 Mar 2006 13:24:44 -0500
Cc: iet-dev <iscsitarget-devel@lists.sourceforge.net>, linux-mips <linux-mips@linux-mips.org>
In-reply-to: <440F1EB2.8050605@tele2.fr>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <440F1EB2.8050605@tele2.fr>
Reply-to: mingz@ele.uri.edu
Sender: linux-mips-bounce@linux-mips.org
thanks for the catch.

could u show us how u did that bypass? thanks.

ming



On Wed, 2006-03-08 at 19:13 +0100, Frederic Temporelli wrote:
> Hello,
> 
> I would like to report an ioctl issue using IET 0.4.13 (iSCSI target) 
> and kernel 2.6.16-rc1, running on mips / SGI O2
> 
> The driver seems to load nicely, but there was no way to do ioctl on the 
> userspace device /dev/ietctl.
> I got such messages in syslog:
> Mar  4 16:47:16 o2 kernel: [4303606.514000] ioctl32(ietd:3448): Unknown 
> cmd fd(4) cmd(81046900){01} arg(7f942ab0) on /dev/ietctl
> 
> => I've been able to resolve the issue by adding a by-pass (goto 
> do_ioctl) in kernel compat_sys_ioctl function (fs/compat.c)  and all is 
> working fine now.
> 
> I don't know if such issue is related to mips only or is due to changes 
> 2.6.16 kernel
> I've also did some tries on x86 with linux 2.6.15.5, all was working 
> fine without needing to change anything in the kernel.
> 
> Did somebody report such issue with IET and recent kernel ?
> May some people from linux-mips tell if such issue is mips specific ?
> 
> Best regards.
> --
> Fred
> 
> 


<Prev in Thread] Current Thread [Next in Thread>