From owner-freebsd-fs Mon Jul 29 14: 0:44 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6729E37B400 for ; Mon, 29 Jul 2002 14:00:42 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB82B43E67 for ; Mon, 29 Jul 2002 14:00:41 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 9BA0DAE27E; Mon, 29 Jul 2002 14:00:41 -0700 (PDT) Date: Mon, 29 Jul 2002 14:00:41 -0700 From: Alfred Perlstein To: "David E. Cross" Cc: fs@freebsd.org, guptar@cs.rpi.edu Subject: Re: UFS Journaling Project Message-ID: <20020729210041.GH76284@elvis.mu.org> References: <200207291714.g6THESc08188@jenolen.cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200207291714.g6THESc08188@jenolen.cs.rpi.edu> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * David E. Cross [020729 10:14] wrote: > > Question: How do we modify struct ufsmount without causing corruption, or > where should we store a pointer to our state information? Several things: first, my apologies for this being kind of silly, my access to sources are very limited now. :) 1) have you just tried _only_ adding a spare field to the start or end of ufsmount struct? 2) newfs, mount_ufs, fsck and tunefs all include ufs/ufs/ufsmount.h possibly something is going wrong there because of kernel/userland mismatch? 3) as a temp workaround why not just use a hashtable based on the ufsmount's address? -- -Alfred Perlstein [alfred@freebsd.org] [#bsdcode/efnet/irc.prison.net] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message