Date: Mon, 29 Jul 2002 14:00:41 -0700 From: Alfred Perlstein <bright@mu.org> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: fs@freebsd.org, guptar@cs.rpi.edu Subject: Re: UFS Journaling Project Message-ID: <20020729210041.GH76284@elvis.mu.org> In-Reply-To: <200207291714.g6THESc08188@jenolen.cs.rpi.edu> References: <200207291714.g6THESc08188@jenolen.cs.rpi.edu>
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? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020729210041.GH76284>