From: Kay Sievers <kay.sievers@vrfy.org>
To: Greg KH <greg@kroah.com>
Cc: Andrew <cmkrnl@speakeasy.net>, linux-kernel@vger.kernel.org
Subject: Re: [Patch] 2.6.10.rc1.bk6 /lib/kobject_uevent.c buffer issues
Date: Sat, 30 Oct 2004 02:00:45 +0200 [thread overview]
Message-ID: <20041030000045.GA13356@vrfy.org> (raw)
In-Reply-To: <20041029231319.GA503@kroah.com>
On Fri, Oct 29, 2004 at 06:13:19PM -0500, Greg KH wrote:
> On Fri, Oct 29, 2004 at 11:28:56PM +0200, Kay Sievers wrote:
> > > But there might still be a problem. With this change, the sequence
> > > number is not sent out the kevent message. Kay, do you think this is an
> > > issue? I don't think we can get netlink messages out of order, right?
> >
> > Right, especially not the events with the same DEVPATH, like "remove"
> > beating an "add". But I'm not sure if the number isn't useful. Whatever
> > we may do with the hotplug over netlink in the future, we will only have
> > /sbin/hotplug for the early boot and it may be nice to know, what events
> > we have already handled...
> >
> > > I'll hold off on applying this patch until we figure this out...
> >
> > How about just reserving 20 bytes for the number (u64 will never be
> > more than that), save the pointer to that field, and fill the number in
> > later?
>
> Ah, something like this instead? I like it, it's even smaller than the
> previous patch. Compile tested only...
I like that. How about the following. It will keep the buffer clean from
random chars, cause the kevent does not have the vector and relies on
the '\0' to separate the strings from each other.
I've tested it. The netlink-hotplug message looks like this:
recv(3, "remove@/class/input/mouse2\0ACTION=remove\0DEVPATH=/class/input/mouse2\0SUBSYSTEM=input\0SEQNUM=961 \0", 1024, 0) = 113
> --------
>
> --- 1.5/lib/kobject_uevent.c 2004-10-22 17:42:27 -05:00
> +++ edited/kobject_uevent.c 2004-10-29 18:07:50 -05:00
> @@ -182,6 +182,7 @@
> char *argv [3];
> char **envp = NULL;
> char *buffer = NULL;
> + char *seq_buff;
> char *scratch;
> int i = 0;
> int retval;
> @@ -258,6 +259,11 @@
> envp [i++] = scratch;
> scratch += sprintf(scratch, "SUBSYSTEM=%s", name) + 1;
>
> + /* reserve space for the sequence,
> + * put the real one in after the hotplug call */
> + envp[i++] = seq_buff = scratch;
> + scratch += sprintf(scratch, "SEQNUM=12345678901234567890") + 1;
+ scratch += strlen("SEQNUM=12345678901234567890") + 1;
> +
> if (hotplug_ops->hotplug) {
> /* have the kset specific function add its stuff */
> retval = hotplug_ops->hotplug (kset, kobj,
> @@ -273,9 +279,7 @@
> spin_lock(&sequence_lock);
> seq = ++hotplug_seqnum;
> spin_unlock(&sequence_lock);
> -
> - envp [i++] = scratch;
> - scratch += sprintf(scratch, "SEQNUM=%lld", (long long)seq) + 1;
> + sprintf(seq_buff, "SEQNUM=%lld", (long long)seq);
+ sprintf(seq_buff, "SEQNUM=%-20lld", (long long)seq);
> pr_debug ("%s: %s %s seq=%lld %s %s %s %s %s\n",
> __FUNCTION__, argv[0], argv[1], (long long)seq,
>
next prev parent reply other threads:[~2004-10-30 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041027142925.GA17484@imladris.arnor.me>
2004-10-27 15:21 ` [Patch] 2.6.10.rc1.bk6 /lib/kobject_uevent.c buffer issues Greg KH
2004-10-27 16:31 ` Andrew
2004-10-29 20:13 ` Greg KH
2004-10-29 21:28 ` Kay Sievers
2004-10-29 23:13 ` Greg KH
2004-10-30 0:00 ` Kay Sievers [this message]
2004-10-30 0:25 ` Kay Sievers
2004-10-30 2:54 ` Kay Sievers
2004-10-30 3:23 ` Andrew
2004-10-31 4:11 ` Kay Sievers
2004-11-01 19:46 ` Greg KH
2004-10-27 17:17 Klaus Dittrich
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=20041030000045.GA13356@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=cmkrnl@speakeasy.net \
--cc=greg@kroah.com \
--cc=linux-kernel@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.