From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] cleanup callout fork
Date: Thu, 11 Mar 2004 01:41:34 +0000 [thread overview]
Message-ID: <20040311014134.GI13045@kroah.com> (raw)
In-Reply-To: <20040310235535.GA31657@vrfy.org>
On Thu, Mar 11, 2004 at 12:55:35AM +0100, Kay Sievers wrote:
> Here I change the callout fork logic.
> The current cersion is unable to read a pipe which is not flushed at once,
> Now we read until it's closed.
Nice.
> The maximum argument count is calculated by the strlen now. We have 100
> chars for our result buffer so we can't have more than 50 parameters.
> So it's much more clear what will happen now and not some magic boundary
> where we use shell behind it.
>
> Parameter can be combined to one by using apostrophes.
>
> this on works now:
> BUS="scsi", PROGRAM="/bin/sh -c 'echo foo3 foo4 foo5 foo6 foo7 foo8 foo9 | sed s/foo9/bar9/'", KERNEL="sda3", NAME="%c{7}"
Very nice. Even if it does allow people to abuse the PROGRAM field :)
> Two new test are also added.
Applied, thanks.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-03-11 1:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 23:55 [PATCH] cleanup callout fork Kay Sievers
2004-03-11 1:41 ` Greg KH [this message]
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=20040311014134.GI13045@kroah.com \
--to=greg@kroah.com \
--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.