linux-kernel - Re: Kernel OOPS and panic on boot in advantech watchdog init

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

Date:	Fri, 19 Sep 2008 15:28:28 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Bryan Donlan <bdonlan@...il.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Kernel OOPS and panic on boot in advantech watchdog init

Alan Cox wrote:
> Looks like yet another Xen bug
>   

No, we've been over this before.

>> [   30.328280] BUG: unable to handle kernel paging request at d6023220
>> [   30.332244] IP: [<c021f6f3>] xen_set_pte+0x3/0x10
>>     
>
> sc520 tries to make an ioremap to read 0xfffefcb0
>
>   
>> [   30.332244]  [<c037be42>] ioremap_page_range+0x1e2/0x280
>> [   30.332244]  [<c023d311>] __ioremap_caller+0x1e1/0x340
>>     
>
> The Xen glue should have either permitted the mapping or failed the
> ioremap attempt with NULL.

Xen glue doesn't get in at that level.  The first Xen knows about the
mapping is the attempt to set a pte with meaningless contents.

I still think the sc520 driver should make some rudimentary attempt to
see if its actually running on a relevant system (ie, an AMD Elan)
before creating iomappings.  I don't know if DMI, cpuid or some other
mechanism would be best though.

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