From: Hannes Reinecke <hare@suse.de>
To: Jeremy Linton <jlinton@tributary.com>,
James Bottomley <jbottomley@parallels.com>
Cc: Kay Sievers <kay@vrfy.org>,
Kai Makisara <kai.makisara@kolumbus.fi>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] st: Do not rewind for SG_IO
Date: Sat, 01 Feb 2014 15:06:51 +0100 [thread overview]
Message-ID: <52ECFF7B.7000401@suse.de> (raw)
In-Reply-To: <52EBD2BB.8020705@tributary.com>
On 01/31/2014 05:43 PM, Jeremy Linton wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 1/31/2014 2:46 AM, Hannes Reinecke wrote:
>
>> This patch make the tape always non-rewinding when SG_IO is used, thus
>> allowing udev to get a proper device id for tapes.
>
> Maybe instead of silently changing the behavior, if you just _HAVE_ to open
> the st device, add an ioctl or st/mt_op that disables the rewind on close.
> That way applications have to explicitly disable the rewind on close.
>
Okay, that sounds like a better alternative.
Point is for udev we simply _have_ to use the given device node.
And when this happens to be set to rewind on close we're doomed.
I'll be drafting up a patch.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
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
next prev parent reply other threads:[~2014-02-01 12:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 8:46 [PATCH] st: Do not rewind for SG_IO Hannes Reinecke
2014-01-31 16:36 ` Jeremy Linton
2014-01-31 16:43 ` Jeremy Linton
2014-02-01 14:06 ` Hannes Reinecke [this message]
2014-02-01 15:23 ` "Kai Mäkisara (Kolumbus)"
2014-02-02 11:42 ` Hannes Reinecke
2014-02-02 19:15 ` "Kai Mäkisara (Kolumbus)"
2014-02-03 6:55 ` Hannes Reinecke
2014-02-03 14:50 ` Jeremy Linton
2014-02-03 15:06 ` Hannes Reinecke
2014-02-03 15:08 ` Jeremy Linton
2014-02-03 20:51 ` Kay Sievers
2014-02-03 21:11 ` James Bottomley
2014-02-03 21:58 ` Jeremy Linton
2014-02-03 22:15 ` Kay Sievers
2014-02-03 22:26 ` Jeremy Linton
2014-02-06 13:10 ` Hannes Reinecke
2014-02-06 13:21 ` Martin K. Petersen
2014-02-06 13:26 ` Hannes Reinecke
2014-02-06 13:50 ` Martin K. Petersen
2014-02-06 14:38 ` James Bottomley
2014-02-06 15:13 ` Hannes Reinecke
2014-02-06 19:21 ` Douglas Gilbert
2014-02-03 21:16 ` Douglas Gilbert
2014-02-03 21:24 ` Kay Sievers
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=52ECFF7B.7000401@suse.de \
--to=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=jlinton@tributary.com \
--cc=kai.makisara@kolumbus.fi \
--cc=kay@vrfy.org \
--cc=linux-scsi@vger.kernel.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.