All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: cxzhang@us.ibm.com
Cc: catalin.marinas@gmail.com, cxzhang@watson.ibm.com,
	czhang.us@gmail.com, jmorris@namei.org,
	linux-kernel@vger.kernel.org, michal.k.k.piotrowski@gmail.com,
	netdev@vger.kernel.org, sds@tycho.nsa.org
Subject: Re: [Patch] kernel memory leak fix for af_unix datagram getpeersec patch
Date: Wed, 02 Aug 2006 15:19:06 -0700 (PDT)	[thread overview]
Message-ID: <20060802.151906.21953222.davem@davemloft.net> (raw)
In-Reply-To: <OF4882A75D.C66DD3D0-ON852571BE.007A0271-852571BE.007A82C3@us.ibm.com>

From: Xiaolan Zhang <cxzhang@us.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.

  reply	other threads:[~2006-08-02 22:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02  6:47 [Patch] kernel memory leak fix for af_unix datagram getpeersec patch Catherine Zhang
2006-08-02 12:49 ` Stephen Smalley
2006-08-02 14:52 ` Michal Piotrowski
2006-08-02 21:11 ` David Miller
2006-08-02 21:14   ` Xiaolan Zhang
2006-08-02 21:32     ` David Miller
2006-08-02 22:18       ` Xiaolan Zhang
2006-08-02 22:19         ` David Miller [this message]
2006-08-02 22:21           ` Xiaolan Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060802.151906.21953222.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=catalin.marinas@gmail.com \
    --cc=cxzhang@us.ibm.com \
    --cc=cxzhang@watson.ibm.com \
    --cc=czhang.us@gmail.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sds@tycho.nsa.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.