linux-kernel - Re: [2.6.23-rc3 possible regression] 8250 claims nonexisting device blocking IO port

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]

Date:	Sun, 19 Aug 2007 21:47:47 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
Cc:	linux-serial@...r.kernel.org,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6.23-rc3 possible regression] 8250 claims nonexisting device blocking IO port

On Saturday 18 August 2007 01:07:55 am Andrey Borzenkov wrote:
> This is related to thread "2.6.22-rc: regression: no irda0 interface (2.6.21 
> was OK), smsc does not find chip" but it is already way too overloaded.
> 
> In 2.6.23 smsc-ircc2 fails to initialize IrDA controller. Apparently because 
> it by default is using the same IO port as ttyS3 and this is now claimed by 
> 8250.

8250 should have claimed ttyS3 in 2.6.21 and earlier.  So from
the 8250 point of view, 2.6.21 and 2.6.23 should behave the same.

>From the smsc-ircc2 point of view, 2.6.21 and 2.6.23 should work
the same except for the additional quirk_smc_enable().  If
2.6.23 is worse than 2.6.21, please try removing the body of
quirk_smc_enable() and see whether that makes 2.6.23 as good
as 2.6.21.

For smsc-ircc2, 2.6.23 is definitely a regression from 2.6.22,
because 8250 stayed out of the way in 2.6.22.  But we had to
revert 8250 back to the 2.6.21 behavior because the change
swapped ttyS0 and ttyS1 on some machines, so we just have to
live with that 8250/smsc-ircc2 conflict for the time being.

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