From owner-freebsd-current Tue Aug 14 23:15:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id B684F37B40B; Tue, 14 Aug 2001 23:15:47 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f7F6Fjn75531; Wed, 15 Aug 2001 08:15:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Greg Lehey Cc: Andrew Kenneth Milton , Michael Lucas , current@FreeBSD.org Subject: Re: devfs and Vinum (was: any -current && vinum problems?) In-Reply-To: Your message of "Wed, 15 Aug 2001 15:01:15 +0930." <20010815150115.V49989@wantadilla.lemis.com> Date: Wed, 15 Aug 2001 08:15:44 +0200 Message-ID: <75529.997856144@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010815150115.V49989@wantadilla.lemis.com>, Greg Lehey writes: >> I'm working on the 16char limit problem as well, but I want to avoid >> allocating memory in incovenient circumstances if at all possible. > >The problem is that I kept having problems with the devfs/vinum >combination even after increasing the size to 96 characters. As I >said to you on IRC quite some time ago now: Yeah, I remember you saying that, and that has made me even more cautious because the only explanation I could find would be stack overruns or places which knew about the "16". But trust me, you are on my list of things to do, but I'm still trying to get rid of my contractors and getting things into a general shape where I will have some spare time again... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message