| 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
| ||
|
Date: 13 Sep 2008 09:09:00 +0200 From: lirc@...telmus.de (Christoph Bartelmus) To: jwilson@...hat.com Cc: stefan.bauer@...tu-chemnitz.de Subject: Re: [PATCH 02/18] lirc serial port receiver/transmitter device driver Hi Jarod, on 12 Sep 08 at 12:24, Jarod Wilson wrote: > On Thursday 11 September 2008 15:49:25 Stefan Bauer wrote: >> Jarod Wilson wrote: >>>> Nothing in this function does anything to assure itself that the port >>>> actually exists and is the right kind of hardware. Maybe that can't >>>> really be done with this kind of device? >>> >>> We should probably try to make sure the port actually exists, but I don't >>> think there's a whole lot (if anything) we can do as far as verifying the >>> device itself. > I've borrowed the simple existence test from > drivers/serial/8250.c::autoconfig(), which tries a few reads and writes from > UART_IER. I think this is probably sufficient for verifying the port is > legit. > > Christoph B., you're definitely much more familiar with serial IR devices > than I am... Is there any sort of test you can think of that we could use to > try to verify the existence of an IR device hooked to the port? Or should we > be happy we at least know there's a port and just assume the IR device is > there? No, I can't think of anything else. OTOH there have never been real problems with this for the past 10 years... Christoph -- 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/
Powered by blists - more mailing lists