linux-kernel - Re: [Patch] kernel memory leak fix for af

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, 2 Aug 2006 18:21:51 -0400
From:	Xiaolan Zhang <cxzhang@...ibm.com>
To:	David Miller <davem@...emloft.net>
Cc:	catalin.marinas@...il.com, cxzhang@...son.ibm.com,
	czhang.us@...il.com, jmorris@...ei.org,
	linux-kernel@...r.kernel.org, michal.k.k.piotrowski@...il.com,
	netdev@...r.kernel.org, sds@...ho.nsa.gov
Subject: Re: [Patch] kernel memory leak fix for af_unix datagram getpeersec patch

I see.  The build was fine under x86 and there are so many warnings that a 
-Werror probably won't work for me.

thanks,
Catherine

David Miller <davem@...emloft.net> wrote on 08/02/2006 06:19:06 PM:

> From: Xiaolan Zhang <cxzhang@...ibm.com>
> Date: Wed, 2 Aug 2006 18:18:07 -0400
> 
> > I did test it with CONFIG_SECURITY disabled, but did not catch the 
warning 
> > -- I verified that the build completes with a valid vmlinux image. 
There 
> > are many warnings (device drivers, and others) during the build and I 
> > didn't do a grep to find which one is specific to my patch.  Next time 

> > I'll do a diff on warnings too.
> 
> Some platforms build their platform code under arch/${ARCH}/foo with
> -Werror added to CFLAGS, sparc64 is one such platform.  So the build
> did break for me.

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