linux-kernel - Re: speakup bug

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: <D9E4F6D133A2410EA4A56217E18CBAD7@hinkle>
Date:	Sat, 3 Mar 2012 20:03:48 -0600
From:	"John G. Heim" <jheim@...h.wisc.edu>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: speakup bug

From: Alan Cox
Sent: Saturday, March 03, 2012 11:39 AM
Subject: Re: speakup bug

>> returns an error code. But it looks as if the region for a serial port,
>> 0x3f8 - 0x3ff,  in ioport_resource cannot be reserved because the entire
>> range from 0x000 through 0xcf7 is already taken by something named "PCI 
>> Bus
>> 0000:00".  Therefore calling request_resource always fails and the driver
> f>or the speech synth errors out.
>
>It's a heirarchical space, so you can allocate things within it. Look
>at /proc/ioports.

# file /proc/ioports
/proc/ioports: empty

>From looking at the code in resource.c, I don't know how you'd get a piece 
of an already allocated range.

It looks like fixing the speakup code to do serial ports right is a lot of 
work. Maybe we can just fix this problem in the mean time.

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