From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [udev] support arguments in callout exec
Date: Thu, 20 Nov 2003 17:31:42 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106934965121296@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106934057408109@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
On Thu, Nov 20, 2003 at 03:59:31AM +0100, Arnd Bergmann wrote:
> On Thursday 20 November 2003 17:07, Kay Sievers wrote:
> > On Thu, Nov 20, 2003 at 01:47:36AM +0100, Arnd Bergmann wrote:
> > > This still doesn't look correct: args[i] will be out of bounds
> > > when the loop has finished on CALLOUT_MAXARG, and the args
> > > array is not zero terminated when calling execve.
> >
> > Good catch, but arg is not NULL if MAXARG is reached - so args is still
> > not terminated :)
>
> > + char *args[CALLOUT_MAXARG];
> > + int i;
> ...
> > + for (i=0; i < CALLOUT_MAXARG; i++) {
> > + args[i] = strsep(&arg, " ");
> > + if (args[i] == NULL)
> > + break;
> > + }
> > + if (args[i]) {
> > + dbg("to many args");
> > + args[i] = NULL;
> > + }
>
> Ok, it's terminated now, but again out of bounds. It should be
> char *args[CALLOUT_MAXARG+1];
> in the beginning or only loop to (CALLOUT_MAXARG - 1).
Oh, oh, oh...
I hope, I don't send more patches than the number of lines added to the code.
Here is #5 :)
thanks,
Kay
[-- Attachment #2: 09-namedev.c-callout-argument-support.diff --]
[-- Type: text/plain, Size: 1320 bytes --]
--- ../udev/namedev.c 2003-11-19 12:56:50.000000000 +0100
+++ namedev.c 2003-11-20 18:29:42.000000000 +0100
@@ -45,6 +45,7 @@
#define TYPE_TOPOLOGY "TOPOLOGY"
#define TYPE_REPLACE "REPLACE"
#define TYPE_CALLOUT "CALLOUT"
+#define CALLOUT_MAXARG 8
static LIST_HEAD(config_device_list);
@@ -480,6 +481,9 @@
pid_t pid;
int value_set = 0;
char buffer[256];
+ char *arg;
+ char *args[CALLOUT_MAXARG];
+ int i;
dbg("callout to %s\n", dev->exec_program);
retval = pipe(fds);
@@ -499,7 +503,22 @@
*/
close(STDOUT_FILENO);
dup(fds[1]); /* dup write side of pipe to STDOUT */
- retval = execve(dev->exec_program, main_argv, main_envp);
+ if (strchr(dev->exec_program, ' ')) {
+ /* callout with arguments */
+ arg = dev->exec_program;
+ for (i=0; i < CALLOUT_MAXARG-1; i++) {
+ args[i] = strsep(&arg, " ");
+ if (args[i] == NULL)
+ break;
+ }
+ if (args[i]) {
+ dbg("to many args - %d", i);
+ args[i] = NULL;
+ }
+ retval = execve(args[0], args, main_envp);
+ } else {
+ retval = execve(dev->exec_program, main_argv, main_envp);
+ }
if (retval != 0) {
dbg("child execve failed");
exit(1);
@@ -528,6 +547,7 @@
strncpy(value, buffer, len);
}
}
+ dbg("callout returned '%s'", value);
close(fds[0]);
res = wait(&status);
if (res < 0) {
next prev parent reply other threads:[~2003-11-20 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 0:47 [udev] support arguments in callout exec Arnd Bergmann
2003-11-20 2:59 ` Arnd Bergmann
2003-11-20 3:21 ` Kay Sievers
2003-11-20 12:31 ` Kay Sievers
2003-11-20 16:07 ` Kay Sievers
2003-11-20 17:31 ` Kay Sievers [this message]
2003-11-20 20:14 ` Arnd Bergmann
2003-11-21 6:50 ` Greg KH
2003-11-21 6:53 ` Greg KH
2003-11-22 18:14 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2003-11-20 1:42 Kay Sievers
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=marc-linux-hotplug-106934965121296@msgid-missing \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.