From owner-freebsd-current Wed Aug 18 8:38: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4319C1595F for ; Wed, 18 Aug 1999 08:38:03 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA47607; Wed, 18 Aug 1999 08:38:15 -0700 (PDT) (envelope-from dillon) Date: Wed, 18 Aug 1999 08:38:15 -0700 (PDT) From: Matthew Dillon Message-Id: <199908181538.IAA47607@apollo.backplane.com> To: Sheldon Hearn Cc: "Mark J. Taylor" , Greg Lehey , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: ccd bugs (was: Kernel hacker tasks seek interested hackers) References: <1717.934983012@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> There is a long as a parameter to ccdbuffer that needs to be a u_long. :> Otherwise, you'll get panics (can't remember where). :> Basically, bcount needs to be a u_long in all cases. : :Que? Are you sure? That means you want to change struct buf, where :b_bcount is declared as long, as well? : :Ciao, :Sheldon. Absolutely not. The maximum size of a struct buf is 64K or 128K or something like that. b_bcount is fine the way it is. There could be a problem with people *using* b_bcount in a complex expression and not casting it higher, but there is no problem with the structural field itself. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message