[LSF/MM TOPIC] Making sure soft SCSI Targets are Valid
Hi All I would like to attend LSF/MM and talk with people about scsi and iscsi testing. I am the author/maintainer for libiscsi which is userspace initiator used primarily by KVM/QEMU. This package also includes a pretty big test suite for mainly SCSI but also a lot of interesting iSCSI tests. As someone hacking on a testsuite, I would like to meet with initiator and target implementors and talk about the existing test suites, and how we can work together from here. What can i bring to FSF/MM? I like SCSI and I like writing tests. I have a big existing testsuite that I think at least some of you can benefit from. I would like to talk to people on how to make the test suite even better. Can we work out a platform where we can build even better and more comprehensive test suites ? etc. regards ronnie sahlberg On Tue, Jan 29, 2013 at 11:13 AM, Lee Duncan wrote: > Hi: > > I'm not sure if there is much interest in this, but I've recently > realized that there is no good free software to validate iSCSI targets, > not to mention FCOE targets, IB soft targets, etc. There's just no way > to know if any change you make is "legal" short of learning to speak > SCSI geek spec (or waiting to see what fails when you make a subtle change). > > So I have been working with the (user-space) libiscsi creator and > maintainer, Ronnie Sahlberg, to enhance his test suite. But this only > addresses iSCSI targets. Some of his tests have already shown problems > like kernel panics when an incorrect bit is injected, showing the need > for such testing. > > It occurs to me it would be most valuable if we had more generic SCSI > tests, not even limited to soft targets, available to developers and > manufacturers. How best to support such tests with our SCSI layer, and > what tests are needed now and in the future may be a good topic for > discussion. > -- > Lee Duncan > SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[LSF/MM TOPIC] Making sure soft SCSI Targets are Valid
Hi, This is my attend request to to co-present a paper with Lee Duncan. regards ronnie sahlberg On Tue, Jan 29, 2013 at 11:13 AM, Lee Duncan wrote: > Hi: > > I'm not sure if there is much interest in this, but I've recently > realized that there is no good free software to validate iSCSI targets, > not to mention FCOE targets, IB soft targets, etc. There's just no way > to know if any change you make is "legal" short of learning to speak > SCSI geek spec (or waiting to see what fails when you make a subtle change). > > So I have been working with the (user-space) libiscsi creator and > maintainer, Ronnie Sahlberg, to enhance his test suite. But this only > addresses iSCSI targets. Some of his tests have already shown problems > like kernel panics when an incorrect bit is injected, showing the need > for such testing. > > It occurs to me it would be most valuable if we had more generic SCSI > tests, not even limited to soft targets, available to developers and > manufacturers. How best to support such tests with our SCSI layer, and > what tests are needed now and in the future may be a good topic for > discussion. > -- > Lee Duncan > SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [LSF/MM TOPIC] Making sure soft SCSI Targets are Valid
On Tue, 2013-01-29 at 11:13 -0800, Lee Duncan wrote: > Hi: > > I'm not sure if there is much interest in this, but I've recently > realized that there is no good free software to validate iSCSI targets, > not to mention FCOE targets, IB soft targets, etc. There's just no way > to know if any change you make is "legal" short of learning to speak > SCSI geek spec (or waiting to see what fails when you make a subtle change). > > So I have been working with the (user-space) libiscsi creator and > maintainer, Ronnie Sahlberg, to enhance his test suite. But this only > addresses iSCSI targets. Some of his tests have already shown problems > like kernel panics when an incorrect bit is injected, showing the need > for such testing. > > It occurs to me it would be most valuable if we had more generic SCSI > tests, not even limited to soft targets, available to developers and > manufacturers. How best to support such tests with our SCSI layer, and > what tests are needed now and in the future may be a good topic for > discussion. +1. Please count me in for this discussion. There are a number of CDB level tests that need to be added to scsi-testsuite.git, and I'd really love to get those interested working on a single codebase for SCSI target verification. --nab -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[LSF/MM TOPIC] Making sure soft SCSI Targets are Valid
Hi: I'm not sure if there is much interest in this, but I've recently realized that there is no good free software to validate iSCSI targets, not to mention FCOE targets, IB soft targets, etc. There's just no way to know if any change you make is "legal" short of learning to speak SCSI geek spec (or waiting to see what fails when you make a subtle change). So I have been working with the (user-space) libiscsi creator and maintainer, Ronnie Sahlberg, to enhance his test suite. But this only addresses iSCSI targets. Some of his tests have already shown problems like kernel panics when an incorrect bit is injected, showing the need for such testing. It occurs to me it would be most valuable if we had more generic SCSI tests, not even limited to soft targets, available to developers and manufacturers. How best to support such tests with our SCSI layer, and what tests are needed now and in the future may be a good topic for discussion. -- Lee Duncan SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
