linux-kernel - Re: [PATCH] crash with /proc/iomem on sparc64

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:	Wed, 18 Mar 2009 23:53:31 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	mpatocka@...hat.com
Cc:	sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] crash with /proc/iomem on sparc64

From: Mikulas Patocka <mpatocka@...hat.com>
Date: Tue, 17 Mar 2009 08:08:08 -0400 (EDT)

> 
> 
> On Tue, 17 Mar 2009, Mikulas Patocka wrote:
> 
> > Hi
> > 
> > When you compile kernel on Sparc64 with heap memory checking and type
> > "cat /proc/iomem", you get a crash, because pointers in struct resource 
> > are uninitialized.
> > 
> > Most code fills struct resource with zeros, so I assume that it is 
> > responsibility of the caller of request_resource to initialized it, not 
> > the responsibility of request_resource functuion.
> > 
> > After 2.6.29 is out, there could be a check for uninitialized fields added 
> > to request_resource to avoid crashes like this.
> > 
> > Mikulas
> 
> I forgot to add:
> 
> Signed-off-by: Mikulas Patocka <mpatocka@...hat.com>

Patch applied and queued up for -stable, thanks a lot.
--
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/