From: Darren Salt <linux@youmustbejoking.demon.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev patch for attributes with trailing spaces in the values
Date: Tue, 17 Feb 2004 01:25:20 +0000 [thread overview]
Message-ID: <4C81E83018%linux@youmustbejoking.demon.co.uk> (raw)
In-Reply-To: <200401301014.51387.meaton@vasco.com>
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
I demand that Kay Sievers may or may not have written...
> On Fri, Jan 30, 2004 at 10:14:51AM +1000, Mark Eaton wrote:
>> The following patch strips off spaces that are often contained at the end
>> of SYSFS_ attributes. (ie lots of printers etc do this). I'm not sure if
>> this should actually be added to udev but I would be curious to hear
>> peoples thoughts as I find it extremly annoying and pointless to have to
>> hexdump the sysfs values to check if there are trailing spaces to write
>> the various rules.
> You may use udevinfo that prints the ready formated attribute for you or
> use the pattern matching if you don't want to count the number of spaces.
> :)
I recently hit this problem when adding a device name (mainly "because I
can") for a CF card reader. Initially, I wasn't aware that there /were/ any
trailing spaces (and I hadn't noticed udevinfo), then I looked again and went
hexdumping...
>> diff -Nru udev-015-orig/namedev.c udev-015/namedev.c
>> --- udev-015-orig/namedev.c 2004-01-23 09:28:36.000000000 +1000
>> +++ udev-015/namedev.c 2004-01-30 08:59:10.000000000 +1000
>> @@ -427,7 +427,10 @@
>> label_found:
>> c = tmpattr->value + strlen(tmpattr->value)-1;
>> if (*c == '\n')
>> - *c = 0x00;
>> + *c-- = 0x00;
> Huh, what if the value is only the '\n'?
Fun and games, of course ;-)
My independently-written version is attached.
--
| Darren Salt | nr. Ashington, | d youmustbejoking,demon,co,uk
| Debian, | Northumberland | s zap,tartarus,org
| RISC OS | Toon Army | @
| When replying, "news"->"ds", "cu"->"co.uk", and validate
By protracting life, we do not deduct one jot from the duration of death.
[-- Attachment #2: trailing-space.patch --]
[-- Type: text/plain, Size: 531 bytes --]
--- udev-016/namedev.c~ 2004-01-31 15:36:18.000000000 +0000
+++ udev-016/namedev.c 2004-02-11 15:09:06.000000000 +0000
@@ -422,9 +422,9 @@
return -ENODEV;
label_found:
- c = tmpattr->value + strlen(tmpattr->value)-1;
- if (*c == '\n')
- *c = 0x00;
+ c = tmpattr->value + strlen(tmpattr->value);
+ while (--c >= tmpattr->value && isspace (*c))
+ *c = 0;
dbg("compare attribute '%s' value '%s' with '%s'",
pair->file, tmpattr->value, pair->value);
if (strcmp_pattern(pair->value, tmpattr->value) != 0)
prev parent reply other threads:[~2004-02-17 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 0:14 udev patch for attributes with trailing spaces in the values Mark Eaton
2004-01-31 1:35 ` Kay Sievers
2004-02-17 1:25 ` Darren Salt [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=4C81E83018%linux@youmustbejoking.demon.co.uk \
--to=linux@youmustbejoking.demon.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).