linux-kernel - Re: [PATCH] alsa: correct nonsensical sysfs device symlinks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Jan 2007 10:57:25 -0500
From:	"Christopher \"Monty\" Montgomery" <xiphmont@...il.com>
To:	"Pierre Ossman" <drzeus@...eus.cx>
Cc:	"Greg KH" <greg@...ah.com>, perex@...e.cz, mclasen@...hat.com,
	jrb@...hat.com, "Lennart Poettering" <lennart@...ttering.net>,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
	fedora-desktop-list@...hat.com
Subject: Re: [PATCH] alsa: correct nonsensical sysfs device symlinks

On 1/25/07, Pierre Ossman <drzeus@...eus.cx> wrote:

> There is some option about deprecated sysfs stuff. Perhaps this is the
> cause of your twisted tree. It's off here:
>
> # CONFIG_SYSFS_DEPRECATED is not set

It is set.  It is also set in the default config, so plently of people
are running with a broken sysfs tree.

I assume we agree that even if that's set, the tree should not be
outright broken like it is (the compatability mode should actually be
compatable, ie, work, right? :-)  Given that, is my patch correct?
What was there (plugging the old 'dev' arg into the new call's
'parent' makes no sense) is clearly wrong.

And it's clear my pacth is incomplete, as it doesn't correct the
device entries for the other entries.

Monty
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/