Re: [PATCH] kernel/param.c: don't use .max when .num is NULL in param_array_set()

2005-03-29 Thread Bert Wesarg
On Tue, 29 Mar 2005, Rusty Russell wrote: > On Sun, 2005-03-27 at 14:57 +0200, Bert Wesarg wrote: > > Hello, > > > > there seems to be a bug, at least for me, in kernel/param.c for arrays > > with .num == NULL. If .num == NULL, the function param_array_set() uses > > &.max for the call to param_

Re: [PATCH] kernel/param.c: don't use .max when .num is NULL in param_array_set()

2005-03-28 Thread Rusty Russell
On Sun, 2005-03-27 at 14:57 +0200, Bert Wesarg wrote: > Hello, > > there seems to be a bug, at least for me, in kernel/param.c for arrays > with .num == NULL. If .num == NULL, the function param_array_set() uses > &.max for the call to param_array(), wich alters the .max value to the > number of a

[PATCH] kernel/param.c: don't use .max when .num is NULL in param_array_set()

2005-03-27 Thread Bert Wesarg
Hello, there seems to be a bug, at least for me, in kernel/param.c for arrays with .num == NULL. If .num == NULL, the function param_array_set() uses &.max for the call to param_array(), wich alters the .max value to the number of arguments. The result is, you can't set more array arguments as the