Re: kdump: resolve sysctl numbers

2011-07-27 Thread Thordur Bjornsson
On 2011 Jul 27 (Wed) at 19:22:34 +0200 (+0200), Jasper Lievisse Adriaanse wrote: > On Wed, Jul 27, 2011 at 10:58:22AM -0400, Ted Unangst wrote: > > On Wed, Jul 27, 2011, Otto Moerbeek wrote: > > > > > +#define SETNAME(name) do { names = (name); limit = nitems(name); } while > > > (0) > > > > use

Re: kdump: resolve sysctl numbers

2011-07-27 Thread Jasper Lievisse Adriaanse
On Wed, Jul 27, 2011 at 10:58:22AM -0400, Ted Unangst wrote: > On Wed, Jul 27, 2011, Otto Moerbeek wrote: > > > +#define SETNAME(name) do { names = (name); limit = nitems(name); } while > > (0) > > userland is not supposed to use nitems I think? But it keeps sneaking > in because the kernel hea

Re: kdump: resolve sysctl numbers

2011-07-27 Thread Otto Moerbeek
On Wed, Jul 27, 2011 at 10:58:22AM -0400, Ted Unangst wrote: > On Wed, Jul 27, 2011, Otto Moerbeek wrote: > > > +#define SETNAME(name) do { names = (name); limit = nitems(name); } while > > (0) > > userland is not supposed to use nitems I think? But it keeps sneaking > in because the kernel he

Re: kdump: resolve sysctl numbers

2011-07-27 Thread Ted Unangst
On Wed, Jul 27, 2011, Otto Moerbeek wrote: > +#define SETNAME(name) do { names = (name); limit = nitems(name); } while (0) userland is not supposed to use nitems I think? But it keeps sneaking in because the kernel headers don't protect it.

kdump: resolve sysctl numbers

2011-07-27 Thread Otto Moerbeek
Hi, This diff (original version from nicm@) adds resolving of systcl numbers to names. e.g.: 914 sysctl CALL __sysctl(hw.pagesize,0x8443e4,0x7f7bb8b8,0,0) 914 sysctl RET __sysctl 0 utrace(2) wil not make release due to ABI/API lock. But this can make if I get reviews and ok's,