linux-kernel - Re: [BUG]2.6.25-rc6:Unable to handle kernel paging request

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: <18400.36670.5918.566965@cargo.ozlabs.ibm.com>
Date:	Wed, 19 Mar 2008 14:57:50 +1100
From:	Paul Mackerras <paulus@...ba.org>
To:	skumar@...ux.vnet.ibm.com
Cc:	linux-kernel@...r.kernel.org,
	Poornima Nayak <Poornima.Nayak@...ibm.com>,
	linuxppc-dev@...abs.org, akpm@...ux-foundation.org
Subject: Re: [BUG]2.6.25-rc6:Unable to handle kernel paging request

Sudhir Kumar writes:

> Unable to handle kernel paging request for data at address
> 0xd00008000000002e

Looks like some driver tried to access I/O port 0x2e without checking
whether there was possibly anything there first.

> Faulting instruction address: 0xc00000000074ded8
> cpu 0x0: Vector: 300 (Data Access) at [c00000003e073aa0]
>     pc: c00000000074ded8: .f71805f_find+0x44/0x32c
>     lr: c00000000074e1f8: .f71805f_init+0x38/0x194
>     sp: c00000003e073d20
>    msr: 8000000000009032
>    dar: d00008000000002e
>  dsisr: 42000000
>   current = 0xc0000000220851c0
>   paca    = 0xc0000000007c2700
>     pid   = 1, comm = swapper
> enter ? for help
> [c00000003e073dc0] c00000000074e1f8 .f71805f_init+0x38/0x194

Looks like it might be the f71805f driver, whatever that is...
Hmmm, drivers/hwmon/f71805f.c looks like it, and indeed it does go
poking around in PCI I/O space with no checks whatever.

I suggest you turn off CONFIG_SENSORS_F71805F.

It doesn't help, of course, that CONFIG_HWMON defaults to y. :(

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