From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make st seekable again
Date: Wed, 09 Mar 2005 20:51:15 +0000 [thread overview]
Message-ID: <1110401474.3116.241.camel@localhost.localdomain> (raw)
In-Reply-To: <200503081911.j28JBlxi016013@hera.kernel.org>
On Maw, 2005-03-08 at 17:25, Linux Kernel Mailing List wrote:
> ChangeSet 1.2030, 2005/03/08 09:25:05-08:00, kai.makisara@kolumbus.fi
>
> [PATCH] make st seekable again
>
> Apparently `tar' errors out if it cannot perform lseek() against a tape. Work
> around that in-kernel.
Unfortunately this isn't a good idea. Allowing tar to read the tape
position makes sense, allowing it to zero the position might but you
have to do major surgery on the driver first because
1. It doesn't use ppos
2. It doesn't do locking on the ppos at all
Also allowing apps to randomly seek and report "ok" when they are
backing up to tape and might really need to see the error is not what
I'd call stable, professional or quality code.
I oppose this change for 2.6.11.3, I think 2.6.12 needs to address the
rest of the mess in that code to make it work (or implement a 'read
only' llseek and
use ppos right)
And -ac won't carry this change.
next parent reply other threads:[~2005-03-09 20:58 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 ` Alan Cox [this message]
2005-03-09 21:58 ` [PATCH] make st seekable again Kai Makisara
2005-03-09 22:27 ` Alan Cox
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=1110401474.3116.241.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--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