linux-kernel - Re: ipw3945 status

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20060730150944.GG23279@thunk.org>
Date:	Sun, 30 Jul 2006 11:09:44 -0400
From:	Theodore Tso <tytso@....edu>
To:	Kasper Sandberg <lkml@...anurb.dk>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>, Jan Dittmer <jdi@....org>,
	Pavel Machek <pavel@...e.cz>,
	Jirka Lenost Benc <jbenc@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	ipw2100-admin@...ux.intel.com
Subject: Re: ipw3945 status

On Sun, Jul 30, 2006 at 05:00:54PM +0200, Kasper Sandberg wrote:
> thats entirely different, if some firmware image is loaded into a card,
> thats that, but running a userspace daemon is just entirely different,
> what would happen if intel for some reason stopped supporting earlier
> cards(as hardware manufactureres do after some time), and linux
> kernel/userspace gets some change, preventing the binary daemon from
> running? then what? we have lost.

Um, last time I checked we could still run some *minix* binaries from
before Linux was born, and we still can run statically linked a.out
programs created over a decade ago.  I don't think this is a serious
objection, given that historically the Linux kernel/userspace syscall
interface has been quite stable.  

Of course, I'd recomend against said driver using sysfs, but Greg K-H
tells us that all breakagaes are the fault of buggy device drivers
(just as supposedly all swsuspend problems are also about buggy device
drivers), so I guess we're OK.  :-)

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