From: Tejun Heo <tj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] uevent: handle duplicate uevent_var keys properly
Date: Thu, 28 Aug 2008 19:00:39 +0200 [thread overview]
Message-ID: <48B6D9B7.2050406@kernel.org> (raw)
In-Reply-To: <20080828164924.GB17475@kroah.com>
Greg KH wrote:
> On Thu, Aug 28, 2008 at 06:31:02PM +0200, Tejun Heo wrote:
>> add_uevent_var() appends the specified variable whether the new entry
>> has duplicate key or not. This patch makes add_uevent_var() to
>> override the existing entry if an entry with the same key is added
>> later. This will be used by CUSE (character device in userland) to
>> fake hotplug events.
>
> Hm, do you have any pointers to CUSE, that sounds interesting.
I'm in the process of sending patches. I'll cc you on the actual postings.
> And how would this change interact with fake hotplug events?
CUSE creates actual devices but those devices are all cuse class
devices. To play nicely with sysfs/hal, the ADD/REMOVE uevents should
have about the same variables as the actual device including the
SUBSYSTEM, so that's where the overriding comes in. CUSE client tells
CUSE that it needs to set such such envs for uevents and CUSE overrides
uevents before sending it out so that sysfs/hal can be fooled.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-08-28 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 16:30 [PATCH 1/2] uevent: don't pass envp_ext[] as format string in kobject_uevent_env() Tejun Heo
2008-08-28 16:31 ` [PATCH 2/2] uevent: handle duplicate uevent_var keys properly Tejun Heo
2008-08-28 16:49 ` Greg KH
2008-08-28 17:00 ` Tejun Heo [this message]
2008-08-28 17:33 ` Greg KH
2008-08-29 7:48 ` Kay Sievers
2008-08-29 8:02 ` Tejun Heo
2008-08-29 13:27 ` Kay Sievers
2008-08-29 13:34 ` Tejun Heo
2008-08-29 13:54 ` Kay Sievers
2008-08-29 15:00 ` Tejun Heo
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=48B6D9B7.2050406@kernel.org \
--to=tj@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox