All of lore.kernel.org
 help / color / mirror / Atom feed
From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: Lee Duncan <lduncan@suse.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org
Subject: [LSF/MM TOPIC] Making sure soft SCSI Targets are Valid
Date: Sun, 10 Mar 2013 16:27:20 -0700	[thread overview]
Message-ID: <CAN05THS92Rw-nFA49UoohcY6ZFfngAH6sDgcq7tdeiVTb3JZfA@mail.gmail.com> (raw)
In-Reply-To: <51081F68.1030808@suse.com>

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 <lduncan@suse.com> 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

      parent reply	other threads:[~2013-03-10 23:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 19:13 [LSF/MM TOPIC] Making sure soft SCSI Targets are Valid Lee Duncan
2013-02-05  5:38 ` Nicholas A. Bellinger
2013-02-25 17:19 ` ronnie sahlberg
2013-03-10 23:27 ` ronnie sahlberg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN05THS92Rw-nFA49UoohcY6ZFfngAH6sDgcq7tdeiVTb3JZfA@mail.gmail.com \
    --to=ronniesahlberg@gmail.com \
    --cc=lduncan@suse.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.