From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Anssi Hannula <anssi.hannula@gmail.com>,
linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org
Subject: Re: sysfs change of input/event devices in 2.6.23rc breaks udev
Date: Mon, 10 Sep 2007 09:24:04 -0400 [thread overview]
Message-ID: <d120d5000709100624s4fd7e68djf8654a4d591cbb5d@mail.gmail.com> (raw)
In-Reply-To: <20070910054448.GA3515@suse.de>
On 9/10/07, Greg KH <gregkh@suse.de> wrote:
> On Mon, Sep 10, 2007 at 01:28:47AM -0400, Dmitry Torokhov wrote:
> > On Sunday 09 September 2007 19:03, Kay Sievers wrote:
> > > On 9/8/07, Anssi Hannula <anssi.hannula@gmail.com> wrote:
> > > >
> > > > However, the change that broke id_path of udev is that
> > > > /sys/class/input/event5/device is now a symlink to the inputX directory
> > > > instead of being the same as the device symlink in inputX directory,
> > > > i.e. to ../../../devices/platform/pcspkr in this case.
> > > >
> > > > Udev id_path uses that directory to construct the ID_PATH variable.
> > > > Should the sysfs structure be reverted or should udev be adapted to
> > > > handle traversing /device symlink twice? I think the former, as there
> > > > should be considerably more time to adapt udev for coming changes in sysfs.
> > >
> > > Udev's path_id script is too dumb to follow the "device" link of
> > > stacked class devices in the CONFIG_SYSFS_DEPRECATED=y layout. Does
> > > this change fix it for you?
> > > http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff_plain;h=b1ac36ff5e3756cefc79967a26280056da31bf6f
> > >
> >
> > Hmm, fixing udev is good but users will not get the change in time. I think we
> > need to adjust SYSFS_DEPRECATED code to produce old results. Something like the
> > patch below. I wonder what Greg would think...
>
> Hm, I don't understand. Didn't the original conversion of the input
> layer by Kay not have this kind of problem? What did your changes do
> differently to cause this driver core change to be needed?
>
If I understand it correctly Kay's convesion had the same issue. With
class devices "device" link points to class_dev->device instead of
class_dev->parent. If you want to keep compatibility with old sysfs
layout when moving from class devices to regular devices then you need
to "skip" couple of parents till you get to "real" device. This only
matters for input because this was the only subsystem with class
devices stacked.
--
Dmitry
next prev parent reply other threads:[~2007-09-10 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 17:08 sysfs change of input/event devices in 2.6.23rc breaks udev Anssi Hannula
2007-09-08 18:29 ` Andrey Borzenkov
2007-09-08 19:38 ` Anssi Hannula
2007-09-08 19:46 ` Andrey Borzenkov
2007-09-09 23:03 ` Kay Sievers
2007-09-10 5:28 ` Dmitry Torokhov
2007-09-10 5:44 ` Greg KH
2007-09-10 13:24 ` Dmitry Torokhov [this message]
2007-09-15 8:05 ` Andrew Morton
2007-09-15 14:18 ` Dmitry Torokhov
2007-09-15 15:46 ` Anssi Hannula
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=d120d5000709100624s4fd7e68djf8654a4d591cbb5d@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=anssi.hannula@gmail.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--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;
as well as URLs for NNTP newsgroup(s).