Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262506AbVCIXFP (ORCPT ); Wed, 9 Mar 2005 18:05:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262536AbVCIXCy (ORCPT ); Wed, 9 Mar 2005 18:02:54 -0500 Received: from clock-tower.bc.nu ([81.2.110.250]:60555 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S262144AbVCIW3L (ORCPT ); Wed, 9 Mar 2005 17:29:11 -0500 Subject: Re: [PATCH] make st seekable again From: Alan Cox To: Kai Makisara Cc: Linux Kernel Mailing List In-Reply-To: References: <200503081911.j28JBlxi016013@hera.kernel.org> <1110401474.3116.241.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1110407237.28860.259.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 09 Mar 2005 22:27:18 +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 931 Lines: 21 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/