From owner-cvs-all Sun Mar 8 10:30:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22555 for cvs-all-outgoing; Sun, 8 Mar 1998 10:30:36 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22500; Sun, 8 Mar 1998 10:30:14 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA15021; Mon, 9 Mar 1998 05:29:06 +1100 Date: Mon, 9 Mar 1998 05:29:06 +1100 From: Bruce Evans Message-Id: <199803081829.FAA15021@godzilla.zeta.org.au> To: dyson@FreeBSD.ORG, gibbs@plutotech.com Subject: Re: cvs commit: src/sys/miscfs/specfs spec_vnops.c Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-sys@FreeBSD.ORG Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk >> Modified files: >> sys/miscfs/specfs spec_vnops.c >> Log: >> Initialize b_resid, and also print out better diagnostics on I/O >> errors. This will allow for better tracking of user error reports. > >What is b_resid initialized to? CAM only touches b_resid when an error >occurs or there is a residual, so I'm hoping it's initialized to 0. >I think that other portions of the tree also expect it to be zero. It is initialized to 0. This is bogus since it is already initialized to 0 (in initpbuf()). It might be useful to initialize it to a bad value to punish portions of the tree expect it to be zero. It used to be abused as the cylinder number for disksort(), so old code won't expect it to be initialized. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message