From owner-freebsd-current@FreeBSD.ORG Sun Nov 9 02:12:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69C2E16A4CE for ; Sun, 9 Nov 2003 02:12:28 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1938143F3F for ; Sun, 9 Nov 2003 02:12:27 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.10/8.12.10) with ESMTP id hA9ACZwv080171; Sun, 9 Nov 2003 11:12:35 +0100 (CET) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.10/8.12.10/Submit) id hA9ACYO6080170; Sun, 9 Nov 2003 11:12:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200311091012.hA9ACYO6080170@spider.deepcore.dk> In-Reply-To: <20031108213139.8791C43FAF@mx1.FreeBSD.org> To: Peter Edwards Date: Sun, 9 Nov 2003 11:12:34 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: current@FreeBSD.ORG Subject: Re: ATAPI-CD corruption since GEOMification (& possible fix) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2003 10:12:28 -0000 It seems Peter Edwards wrote: > With a -current built after atapi-cd was changed over to GEOM, reads > from a filesystem mounted on a CD device are being corrupted, with > junk being inserted into the file from offset 63489 onwards. > > I had a quick look around atapi-cd.c, and I think I spotted the > problem: applying this patch certainly stopped the corruption > I was seeing. Anyone else seeing this? Can someone verify that > this is indeed the correct fix? Yeps looks like what I intended, but apprarently didn't type :( Fix committed, thanks! -Søren