| 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
| ||
|
Message-ID: <20110330212440.794e85de@lxorguk.ukuu.org.uk> Date: Wed, 30 Mar 2011 21:24:40 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Daniel Palmer <me@...ielpalmer.co.uk> Cc: linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: PATA_ARTOP reads byte from PCI IO port without mapping it to the right address. On Wed, 30 Mar 2011 20:48:26 +0100 Daniel Palmer <me@...ielpalmer.co.uk> wrote: > > > That is the PCI port address. > > I don't pretend to understand most of this fully. > On the board the PCI address space/PCI controller is apparently at > 0xfe240000 > So I guess that when that byte is read it should read from 0xfe240000 + > 0x1400? > That doesn't happen and a read happens at 0x1400 and an oops results. > I don't know enough to point the finger really. > > There are probably only 2 people using this board still too. So I doubt > it really matters. :) That sounds like the inb() function has been broken by a change perhaps by some related board change - if your I/O is mapped as you describe I'd expect inb() to be implemented as something like return *(volatile u8 *)(0xfe2400 + addr) Might be worth bisecting between a good and bad release as it ought to be easy to find 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/
Powered by blists - more mailing lists