linux-kernel - Re: [PATCH] V4L1: make PMS not auto-grab port 0x250

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: <20080809225502.27b38a9d@lxorguk.ukuu.org.uk>
Date:	Sat, 9 Aug 2008 22:55:02 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Rene Herman <rene.herman@...access.nl>
Cc:	Andrew Morton <akpm@...l.org>, Ingo Molnar <mingo@...e.hu>,
	video4linux-list@...hat.com,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] V4L1: make PMS not auto-grab port 0x250

> > Just apply a tiny bit of rational thought here. There is exactly ONE 
> > Ingo.
> 
> And as you say yourself -- close to exactly 1 person who still has this 
> hardware and closer still to 0 who use it. Really, you contradict yourself:

Consider the posibility that I might be talking about the general case
here. And if there are two people with the PMS card thats the general
case 8)

> We know this driver breaks the boot during useful kernel work. We know 
> that changing it has about a 0.0001% percent change of mattering to 
> anyone and then only as long as all those person can't be bothered to 
> setup a value in his modprobe.conf.

It never breaks anything for anyone as a module, only compiled in. Which
despite your moans about 'factual' things is a fact.

Can I suggest a rather more elegant solution would be to add a
"CONFIG_UNSAFE_PROBES" tristate (so you can decide if you want no unsafe
probing devices, unsafe probing devices only as modules, or anything goes)

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