From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Amit D. Chaudhary" Subject: Re: SCSI_IOCTL_GET_IDLUN Date: Wed, 12 May 2004 12:34:06 -0700 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <40A27C2E.6040205@comcast.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from rwcrmhc12.comcast.net ([216.148.227.85]:20894 "EHLO rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP id S265192AbUELTgI (ORCPT ); Wed, 12 May 2004 15:36:08 -0400 In-Reply-To: List-Id: linux-scsi@vger.kernel.org To: Jim.Roarick@Bull.com Cc: linux-scsi@vger.kernel.org Jim, It seems like the problem is due to an addition in 2.6.5 to drivers/scsi/st.c, st_ioctl() function to make a call scsi_cmd_ioctl() which is in drivers/block/scsi_ioctl() before making a call to scsi_ioctl() scsi_cmd_ioctl() does put a 0 instead of proper data for SCSI_IOCTL_GET_IDLUN, SCSI_IOCTL_GET_BUS_NUMBER, etc. Let's wait for a day or so to see if someone else responds that there is might be a work in progress. Amit Jim.Roarick@Bull.com wrote: > We have an application that does an open of a pseudo tape device ( > /dev/st(x) ), followed by an ioctl (SCSI_IOCTL_GET_IDLUN) to get the > address information. This worked fine in 2.4.6-20 and 2.6.1 but in 2.6.5 > returns null with no error indicated. > > Did something change in mid-stream and, if so, how does one make it work > again? > > Sorry for the lack of a low level description, I am neither a kernel > person or a driver person, merely an application person. > > > - > To unsubscribe from this list: send the line "unsubscribe linux-scsi" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >