From owner-freebsd-fs Mon Jul 29 14: 8:56 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 EBBE037B400 for ; Mon, 29 Jul 2002 14:08:53 -0700 (PDT) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DB0343E4A for ; Mon, 29 Jul 2002 14:08:53 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from jenolen.cs.rpi.edu (jenolen.cs.rpi.edu [128.213.12.42]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA85668; Mon, 29 Jul 2002 17:08:50 -0400 (EDT) Received: from jenolen.cs.rpi.edu (crossd@localhost) by jenolen.cs.rpi.edu (8.11.6+Sun/8.9.3) with ESMTP id g6TL8ob08531; Mon, 29 Jul 2002 17:08:50 -0400 (EDT) Message-Id: <200207292108.g6TL8ob08531@jenolen.cs.rpi.edu> X-Authentication-Warning: jenolen.cs.rpi.edu: crossd owned process doing -bs To: Alfred Perlstein Cc: "David E. Cross" , fs@freebsd.org, guptar@cs.rpi.edu, crossd@cs.rpi.edu Subject: Re: UFS Journaling Project In-Reply-To: Message from Alfred Perlstein of "Mon, 29 Jul 2002 14:00:41 PDT." <20020729210041.GH76284@elvis.mu.org> References: <200207291714.g6THESc08188@jenolen.cs.rpi.edu> <20020729210041.GH76284@elvis.mu.org> Date: Mon, 29 Jul 2002 17:08:49 -0400 From: "David E. Cross" 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? Not yet, we wanted to group this with some of the other UFS extensions. > > 2) newfs, mount_ufs, fsck and tunefs all include ufs/ufs/ufsmount.h > possibly something is going wrong there because of kernel/userland > mismatch? This isn't even to the point where userland is an issue, it is right ad the kernel tries to mount the rootfs with the modified UFS code. > > 3) as a temp workaround why not just use a hashtable based on the > ufsmount's address? That is evil beyond words. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message