From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT] Security changes for 2.6.29
Date: Mon, 29 Dec 2008 14:30:48 +1100 (EST) [thread overview]
Message-ID: <alpine.LRH.1.10.0812291429520.14432@tundra.namei.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0812281651480.3082@localhost.localdomain>
On Sun, 28 Dec 2008, Linus Torvalds wrote:
> On Mon, 29 Dec 2008, David Howells wrote:
> >
> > Does this fix the warning? My compiler doesn't show it; of course, I'm not
> > using gcc-4.3.2, but something older.
>
> Yup, this seems to fix it for me in my quick test. It seems that not
> initializing the pointer for the error case makes gcc unhappy.
>
This fix is available to be pulled:
The following changes since commit
3c92ec8ae91ecf59d88c798301833d7cf83f2179:
Linus Torvalds (1):
Merge branch 'next' of git://git.kernel.org/.../paulus/powerpc
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6 for-linus
David Howells (1):
KEYS: Fix variable uninitialisation warnings
security/keys/keyctl.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2008-12-29 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 1:07 [GIT] Security changes for 2.6.29 James Morris
2008-12-28 20:32 ` Linus Torvalds
2008-12-29 0:41 ` David Howells
2008-12-29 0:53 ` Linus Torvalds
2008-12-29 3:30 ` James Morris [this message]
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=alpine.LRH.1.10.0812291429520.14432@tundra.namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox