From: Dominik Brodowski <linux@brodo.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support
Date: Wed, 9 Apr 2003 21:48:54 +0200 [thread overview]
Message-ID: <20030409194854.GA4449@brodo.de> (raw)
In-Reply-To: <3E9354D3.8090805@pobox.com>
On Tue, Apr 08, 2003 at 07:01:39PM -0400, Jeff Garzik wrote:
> >As strings can't be passed to userspace in file2alias.c, I've chosen the
> >crc32 value of the string as the matching identifier for the userspace
> >hotplug script.
>
> This sounds like a problem to be solved, not worked around... the
> source should have the strings presented directly, and I'm sure a
> creative and smart person such as yourself can conceive of at least
> one... ;-)
OK, there might be a way to do this (and yes, I can think of one...).
However, I doubt it makes sense: using strings in depmod.c and in the
hotplug utilities is even worse than in file2alias.c. For example,
whitespace is used as delimitier for the values being parsed in hotplug
scripts. So I think the better (as simpler and thus more difficult to break)
approach is using crc32.
Dominik
next prev parent reply other threads:[~2003-04-09 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 20:56 [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support Dominik Brodowski
2003-04-08 21:20 ` Jeff Garzik
2003-04-08 21:34 ` Dominik Brodowski
2003-04-08 23:01 ` Jeff Garzik
2003-04-09 19:48 ` Dominik Brodowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 22:31 Jean Tourrilhes
2003-04-08 22:56 ` Jeff Garzik
2003-04-09 0:05 ` Jean Tourrilhes
2003-04-09 6:38 ` Dominik Brodowski
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=20030409194854.GA4449@brodo.de \
--to=linux@brodo.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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