From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make st seekable again
Date: Wed, 09 Mar 2005 22:27:18 +0000 [thread overview]
Message-ID: <1110407237.28860.259.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0503092338300.6756@kai.makisara.local>
On Mer, 2005-03-09 at 21:58, Kai Makisara wrote:
> While waiting for the application to be fixed, it was decided to restore
> the old behaviour of the tape drivers.
Which means tar won't get fixed 8(
> I don't think implementing proper read-only lseek for tapes is worth the
> trouble (reliable tracking of the current location is tricky). Purist
> kernels can refuse lseeks. Pragmatic kernels can allow lseeks until
> refusing those won't break common applications.
The problem is the existing behaviour code isn't just 'not useful' its
badly broken. No locking, no overflow checks, updates the wrong variable
etc. It is asking for nasty accidents with critical user data.
Alan
next prev parent reply other threads:[~2005-03-09 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503081911.j28JBlxi016013@hera.kernel.org>
2005-03-09 20:51 ` [PATCH] make st seekable again Alan Cox
2005-03-09 21:58 ` Kai Makisara
2005-03-09 22:27 ` Alan Cox [this message]
2005-03-10 11:49 ` Bill Davidsen
2005-03-10 12:10 ` Arjan van de Ven
2005-03-10 16:43 ` Alan Cox
2005-03-10 16:56 ` Bill Davidsen
2005-03-10 17:13 ` Arjan van de Ven
2005-03-10 17:58 ` Alan Cox
[not found] <fa.i3f7d9s.30m8rg@ifi.uio.no>
[not found] ` <fa.l4kuq52.e6001g@ifi.uio.no>
2005-03-10 0:43 ` Bodo Eggert
2005-03-10 20:01 ` Willy Tarreau
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=1110407237.28860.259.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Kai.Makisara@kolumbus.fi \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox