On Friday, November 13, 2015 04:47:53 PM Randall Stewart wrote: > > On Nov 13, 2015, at 4:43 PM, Bryan Drewery <bdrew...@freebsd.org> wrote: > > > On 11/13/2015 1:24 PM, Randall Stewart wrote: > >> Looking at the patch, we need a define of your > >> > >> _callout_stop_safe > >> > >> and we need to switch > >> > >> callout_stop()’s define to use the new _callout_stop_safe() > > > > For both cases, there would be no reason to have new code call my > > wrapper. The defines in my patch are fine for new code. The "new" > > _callout_stop_safe function is just for existing modules. > > > > I think the historical consensus is to not commit my patch though as > > people should recompile their modules when the kernel is updated, before > > rebooting into the new kernel even. > > I did (as Han’s suggested) bump the FreeBSD version number.. > > So maybe thats good enough.
I think this will be problematic to MFC. It would be both an API and ABI change for existing modules, and callout(9) is a fairly common API that you would expect modules to use (not some internal thing that few if any modules use). The ABI stub would need to return the old values (so map -1 to 0). Changing the API in this way though means that code can silently be recompiled and break (there's no compile error, etc. The API only changes in that the semantics of the functions change). -- John Baldwin _______________________________________________ svn-src-head@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"