| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <47BEFF5F.9020002@cs.wisc.edu> Date: Fri, 22 Feb 2008 10:59:11 -0600 From: Mike Christie <michaelc@...wisc.edu> To: markh@...pro.net CC: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: New 2.6.24.2 SG_IO SCSI problems Mike Christie wrote: > Mark Hounschell wrote: >> I seem to have run into some sort of regression in the SG_IO interface >> of 2.6.24.2. I have an application that up until 2.6.24 worked fine. >> The 2.6.23.16 kernel works fine. >> >> During reads I get these kernel messages. Writes and other functions >> _seem_ OK. Actually basic >> reads are working. Its with large BC reads using an io_vec list that >> the problem shows up. >> > > Are you doing SG_IO to the sg device (/dev/sg*) or to the block device > (/dev/sdX)? If you are doing SG_IO to the sg device, then I know of one regression (well not regression exactly, but I fixed a bug but the patch got partially overwritten by another patch and that caused a new bug). Both bugs are fixed in 2.6.25-rc2. Could you try that out if you are doing SG_IO to the sg device. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists