From: Bert Wesarg <wesarg@informatik.uni-halle.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] kernel/param.c: don't use .max when .num is NULL in param_array_set()
Date: Sun, 27 Mar 2005 14:57:24 +0200 (MEST) [thread overview]
Message-ID: <Pine.GSO.4.56.0503271455190.25037@turing> (raw)
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 last time you set the parameter.
example:
# a module 'example' with
# static int array[10] = { 0, };
# module_param_array(array, int, NULL, 0644);
$ insmod example.ko array=1,2,3
$ cat /sys/module/example/parameters/array
1,2,3
$ echo "4,3,2,1" > /sys/module/example/parameters/array
$ dmesg | tail -n 1
kernel: array: can take only 3 arguments
Patch is against 2.6.12-rc1.
Signed-off-by: Bert Wesarg <wesarg@informatik.uni-halle.de>
--- linux-2.6.12-rc1.orig/kernel/params.c 2005-03-27 14:44:00.000000000 +0200
+++ linux-2.6.12-rc1/kernel/params.c 2005-03-27 14:45:55.000000000 +0200
@@ -314,9 +314,10 @@ int param_array(const char *name,
int param_array_set(const char *val, struct kernel_param *kp)
{
struct kparam_array *arr = kp->arg;
+ unsigned int temp_num;
return param_array(kp->name, val, 1, arr->max, arr->elem,
- arr->elemsize, arr->set, arr->num ?: &arr->max);
+ arr->elemsize, arr->set, arr->num ?: &temp_num);
}
int param_array_get(char *buffer, struct kernel_param *kp)
next reply other threads:[~2005-03-27 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 12:57 Bert Wesarg [this message]
2005-03-29 6:05 ` Rusty Russell
2005-03-29 10:07 ` Bert Wesarg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0503271455190.25037@turing \
--to=wesarg@informatik.uni-halle.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®