Date: Mon, 29 Jul 2002 17:08:49 -0400 From: "David E. Cross" <crossd@cs.rpi.edu> To: Alfred Perlstein <bright@mu.org> Cc: "David E. Cross" <crossd@cs.rpi.edu>, fs@freebsd.org, guptar@cs.rpi.edu, crossd@cs.rpi.edu Subject: Re: UFS Journaling Project Message-ID: <200207292108.g6TL8ob08531@jenolen.cs.rpi.edu> In-Reply-To: Message from Alfred Perlstein <bright@mu.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
> * David E. Cross <crossd@cs.rpi.edu> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200207292108.g6TL8ob08531>