All of lore.kernel.org
 help / color / mirror / Atom feed
From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: Lee Duncan <lduncan@suse.com>, linux-scsi@vger.kernel.org
Subject: [LSF/MM TOPIC] Making sure soft SCSI Targets are Valid
Date: Mon, 25 Feb 2013 09:19:15 -0800	[thread overview]
Message-ID: <CAN05THS0VdznK8N3A-jR6yBP+JGcDmud1YohXwKqV9czdba+NA@mail.gmail.com> (raw)
In-Reply-To: <51081F68.1030808@suse.com>

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 <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-02-25 17:19 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 [this message]
2013-03-10 23:27 ` ronnie sahlberg

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=CAN05THS0VdznK8N3A-jR6yBP+JGcDmud1YohXwKqV9czdba+NA@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.