Date: Sun, 1 Sep 2013 10:41:57 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: fixing "umount -f" for the NFS client Message-ID: <1247162688.16775666.1378046517881.JavaMail.root@uoguelph.ca> In-Reply-To: <alpine.GSO.1.10.1308312130220.16692@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Benjamin Kaduk wrote: > On Fri, 30 Aug 2013, Rick Macklem wrote: > > > Kostik wrote: > >> On Thu, Aug 29, 2013 at 07:43:34PM -0400, Rick Macklem wrote: > >>>>> I assume I would also need to bump __FreeBSD_version (and maybe > >>>>> VFS_VERSION?). > >>>> I think you could avoid it. > >>>> > >>> Do you mean I don't need to bump __FreeBSD_version or VFS_VERSION > >>> or both? > >> I do not see much sense in bumping either of them. > >> You might want to bump __FreeBSD_version when merging to stable. > > Please do bump __FreeBSD_version when merging to stable. I will not > make > much noise about -current at the moment, as I'm behind on tracking > it. > Actually, I'm "on the fence" as to whether or not this one should be MFC'd, due to the VFS ABI breakage. Since you (well, actually OpenAFS;-) are the main guy affected by VFS ABI breakage these days, maybe you'd like to comment on this? Also, if anyone else has an opinion w.r.t. MFC'ng a patch that adds a VFS op and, therefore, breaks the VFS ABI, please feel free to comment. Thanks, rick ps: And, yes, I will bump __FreeBSD_version of I end up doing the MFC. > Thanks, > > Ben >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1247162688.16775666.1378046517881.JavaMail.root>