linux-kernel - Problem with /proc/iomem on ARM

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-next>] [day] [month] [year] [list]

Date:	Wed, 1 Jul 2009 13:32:19 -0400
From:	"H Hartley Sweeten" <hartleys@...ionengravers.com>
To:	<kay.sievers@...y.org>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Problem with /proc/iomem on ARM

Hello Kay,

I just noticed a problem with /proc/iomem on my ARM system
that I think was introduced by your patch:

commit 1d559e29138834bbcdf34ac072232bf543bfc4e0
Author: Kay Sievers <kay.sievers@...y.org>
Date:   Tue Jan 6 10:44:43 2009 -0800

    arm: struct device - replace bus_id with dev_name(), dev_set_name()

    Cc: Russell King <rmk@....linux.org.uk>
    Signed-off-by: Kay Sievers <kay.sievers@...y.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>

On my ep93xx ARM system I have three pl010 uarts: "apb:uart1",
"apb:uart2", and "apb:uart3".  For /proc/iomem I used to see:

/ # cat proc/iomem
...
808c0000-808c0fff : apb:uart1
  808c0000-808c003f : uart-pl010
808d0000-808d0fff : apb:uart2
  808d0000-808d003f : uart-pl010
808e0000-808e0fff : apb:uart3
  808e0000-808e003f : uart-pl010
...

Now it shows up as:

/ # cat proc/iomem
...
808c0000-808c0fff : <BAD>
  808c0000-808c003f : uart-pl010
808d0000-808d0fff : <BAD>
  808d0000-808d003f : uart-pl010
808e0000-808e0fff : <BAD>
  808e0000-808e003f : uart-pl010
...

Is this a regression or is there something else going on?

This was seen with kernel 2.6.30.  I havn't looked at /proc/iomem for
a while so I'm not sure when this first started.

Regards,
Hartley
--
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/