linux-kernel - Re: removal of sysfs wext extension broke on F16

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]

Message-ID: <1352795227.9466.8.camel@jlt4.sipsolutions.net>
Date:	Tue, 13 Nov 2012 09:27:07 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Dave Airlie <airlied@...il.com>
Cc:	John Linville <linville@...driver.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: removal of sysfs wext extension broke on F16

On Tue, 2012-11-13 at 07:52 +1000, Dave Airlie wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=875328
> 
> blamed for breaking wireless.
> https://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=35b2a113cb0298d4f9a1263338b456094a414057
> 
> apparantly the initscripts used the sysfs directory existance as a
> check, so maybe either back this out or bring back just the subdirs.

OK. I really thought nobody was using it, but we can of course revert it
for Fedora's benefit, it's optional anyway.

FWIW, for most drivers you could check if the sys/class/net/$1/phy80211
symlink exists, but that doesn't work for older wext-only drivers (or
say the crap Broadcom binary STA driver.)

Should I revert it and send it in my next pull request?

johannes

--
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/