Date: Sat, 10 Nov 2018 00:18:13 -0800 From: Eitan Adler <lists@eitanadler.com> To: Brooks Davis <brooks@freebsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r340294 - head/sys/compat/freebsd32 Message-ID: <CAF6rxgmjGQz%2B1wgE%2BUKzm%2B7K-wJHBNTaTEUaPgHsRN5eB256PQ@mail.gmail.com> In-Reply-To: <20181109181901.GA61841@spindle.one-eyed-alien.net> References: <201811091803.wA9I31ie014903@repo.freebsd.org> <20181109181901.GA61841@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 9 Nov 2018 at 10:19, Brooks Davis <brooks@freebsd.org> wrote: > > On Fri, Nov 09, 2018 at 06:03:01PM +0000, Brooks Davis wrote: > > Author: brooks > > Date: Fri Nov 9 18:03:01 2018 > > New Revision: 340294 > > URL: https://svnweb.freebsd.org/changeset/base/340294 > > > > Log: > > Fix a number of bugs in freebsd32's capabilities.conf. > > > > Bugs range from failure to update after changing syscall implementaion > > names to using the wrong name. Somewhat confusingly, the name in > > capabilities.conf is exactly the string that appears in syscalls.master, > > not the name with a COMPAT* prefix which is the actual function name. > > > > Found while making a change to use the default capabilities.conf. Is there any automated way to detect this in the future? Can we add some test that detect non-existent syscalls or the like? -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgmjGQz%2B1wgE%2BUKzm%2B7K-wJHBNTaTEUaPgHsRN5eB256PQ>