From: Greg KH <gregkh@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
Arjan van de Ven <arjan@infradead.org>,
Linus Torvalds <torvalds@osdl.org>,
Kay Sievers <kay.sievers@suse.de>,
Pekka J Enberg <penberg@cs.Helsinki.FI>,
Adrian Bunk <bunk@stusta.de>, Robert Love <rml@novell.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>
Subject: Re: sysfs regressions (was: 2.6.16-rc4: known regressions)
Date: Wed, 22 Feb 2006 09:47:29 -0800 [thread overview]
Message-ID: <20060222174729.GA10882@suse.de> (raw)
In-Reply-To: <20060222171714.GC19733@merlin.emma.line.org>
On Wed, Feb 22, 2006 at 06:17:14PM +0100, Matthias Andree wrote:
> Christoph Hellwig schrieb am 2006-02-22:
>
> > And to continue the rant: the broken mount uevent feature (which
> > can't work right) got in without any serious review through the
> > driver model tree. just as all those break udev/etc patches that
> > cause all these userland breakages for those people brave enough
> > to use udev and surrounding bits.
> >
> > Folks, we need to stop breaking sysfs interface all the time. Having
> > attributes on objects is real nice from many perspectives, but it's
> > also a burden because the internal object model is now seen by the
> > outside world. That means anything involving sysfs needs a careful
> > design not random patching as the driver model core people appear to
> > do.
>
> Oh, and while we're at it: perhaps someone should revert the patch that
> caused Douglas Gilbert to chase incompatible sysfs changes in his
> user-space applications. It's pretty sad to see random breakage,
> apparently by randomly changing / to : in paths from what I discern from
> Doug's Changelog. (No, I don't have the background handy, neither would
> I care; I just see the application chasing sysfs changes, and that's
> enough to complain.)
No, that fixed a real bug where sysfs would create multiple symlinks
with the same name in the same directory. That _had_ to be fixed, as
even Douglas's old tools couldn't handle that properly :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-02-22 17:47 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 22:45 Linux 2.6.16-rc4 Linus Torvalds
2006-02-17 23:14 ` 2.6.16-rc4: known regressions Adrian Bunk
2006-02-17 23:14 ` Adrian Bunk
2006-02-19 11:06 ` Pekka Enberg
2006-02-19 11:06 ` Pekka Enberg
2006-02-19 14:54 ` Adrian Bunk
2006-02-19 17:50 ` Pekka Enberg
2006-02-19 21:14 ` Pekka Enberg
2006-02-20 1:02 ` Greg KH
2006-02-20 7:08 ` Pekka J Enberg
2006-02-21 22:51 ` Pekka Enberg
2006-02-21 22:57 ` Kay Sievers
2006-02-21 23:33 ` Andrew Morton
2006-02-22 0:04 ` Kay Sievers
2006-02-22 0:15 ` Mark Lord
2006-02-22 0:21 ` Andrew Morton
2006-02-22 0:34 ` Linus Torvalds
2006-02-22 0:46 ` Con Kolivas
2006-02-22 1:06 ` Linus Torvalds
2006-02-22 11:21 ` Theodore Ts'o
2006-02-22 14:25 ` uswsusp & initrd -- was " Pavel Machek
2006-02-22 15:48 ` Joel Becker
2006-02-22 16:25 ` Theodore Ts'o
2006-02-22 17:33 ` Gabor Gombas
2006-02-22 17:57 ` Linus Torvalds
2006-02-22 18:37 ` Christian Trefzer
2006-02-22 18:59 ` Joel Becker
2006-02-22 19:18 ` Greg KH
2006-02-22 19:29 ` Arjan van de Ven
2006-02-22 19:40 ` Greg KH
2006-02-22 20:45 ` Jens Axboe
2006-02-22 22:51 ` Greg KH
2006-02-23 6:39 ` Jens Axboe
2006-02-23 17:29 ` Martin Bligh
2006-02-23 17:52 ` Greg KH
2006-02-23 18:01 ` Martin Bligh
2006-02-23 18:04 ` Arjan van de Ven
2006-02-23 20:26 ` Benjamin LaHaise
2006-02-24 23:42 ` Eric W. Biederman
2006-02-22 19:39 ` Linus Torvalds
2006-02-22 19:54 ` Andrew Morton
2006-02-22 20:02 ` Arjan van de Ven
2006-02-22 20:12 ` Linus Torvalds
2006-02-22 20:44 ` Andrew Morton
2006-02-22 20:26 ` Greg KH
2006-02-23 5:28 ` Jody McIntyre
2006-02-22 20:57 ` Diego Calleja
2006-02-22 21:19 ` Russell King
2006-02-22 21:30 ` Greg KH
2006-02-22 20:47 ` Bryan O'Sullivan
2006-02-22 19:07 ` Greg KH
2006-02-22 17:06 ` Matthias Andree
2006-02-23 12:36 ` Paulo Marques
2006-02-22 10:49 ` Diego Calleja
2006-02-22 7:06 ` Pekka J Enberg
2006-02-22 15:27 ` Kay Sievers
2006-02-22 15:44 ` Linus Torvalds
2006-02-22 16:03 ` Arjan van de Ven
2006-02-22 16:11 ` Christoph Hellwig
2006-02-22 17:17 ` sysfs regressions (was: 2.6.16-rc4: known regressions) Matthias Andree
2006-02-22 17:47 ` Greg KH [this message]
2006-02-22 16:18 ` 2.6.16-rc4: known regressions David Zeuthen
2006-02-22 16:35 ` Christoph Hellwig
2006-02-22 16:46 ` David Zeuthen
2006-02-22 16:51 ` Christoph Hellwig
2006-02-22 17:08 ` Linus Torvalds
2006-02-22 17:31 ` Linus Torvalds
2006-02-22 18:04 ` Al Viro
2006-02-23 3:01 ` John Stoffel
2006-02-22 17:51 ` Al Viro
2006-02-22 17:55 ` Christoph Hellwig
2006-02-22 18:10 ` Al Viro
2006-02-22 19:25 ` David Zeuthen
2006-02-22 17:10 ` Al Viro
2006-02-22 17:10 ` grundig
2006-02-22 17:14 ` Martin Bligh
2006-02-23 4:17 ` Theodore Ts'o
2006-02-22 18:10 ` Pekka Enberg
2006-02-22 8:28 ` Arjan van de Ven
2006-02-17 23:27 ` Linux 2.6.16-rc4 Nigel Cunningham
2006-02-18 8:59 ` Edmondo Tommasina
2006-02-18 9:19 ` Gene Heskett
2006-02-18 10:20 ` Con Kolivas
2006-02-18 11:26 ` Gene Heskett
2006-02-18 16:04 ` Jean Delvare
2006-02-22 22:02 ` Linux 2.6.16-rc4 edac oops Mark Rustad
2006-02-24 11:09 ` Andrew Morton
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=20060222174729.GA10882@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=hch@infradead.org \
--cc=johnstul@us.ibm.com \
--cc=kay.sievers@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.Helsinki.FI \
--cc=rml@novell.com \
--cc=torvalds@osdl.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.