From: Davidlohr Bueso <dave@stgolabs.net>
To: ethan zhao <ethan.zhao@oracle.com>
Cc: Stephen Smalley <stephen.smalley@gmail.com>,
Ethan Zhao <ethan.kernel@gmail.com>,
Manfred Spraul <manfred@colorfullife.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Eric Paris <eparis@parisplace.org>,
Paul Moore <paul@paul-moore.com>, selinux <selinux@tycho.nsa.gov>,
linux-security-module@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
ethan.kernel@gmail.conm
Subject: Re: [PATCH] Selinux/hooks.c: Fix a NULL pointer dereference caused by semop()
Date: Thu, 22 Jan 2015 19:30:03 -0800 [thread overview]
Message-ID: <1421983803.24914.3.camel@stgolabs.net> (raw)
In-Reply-To: <54C1AFA2.8040900@oracle.com>
On Fri, 2015-01-23 at 10:19 +0800, ethan zhao wrote:
> > If not, what kernel
> > version were you running when you triggered the bug?
> To be honest, a kernel from distro, but not released, but before we
> get it clear, we wouldn't public more.
Sheesh, could Oracle be any more (ridiculously) secretive about what the
hell kernel(s) they run... it's like pulling teeth. *sigh*
next prev parent reply other threads:[~2015-01-23 3:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 9:18 [PATCH] Selinux/hooks.c: Fix a NULL pointer dereference caused by semop() Ethan Zhao
2015-01-20 14:10 ` Stephen Smalley
2015-01-20 18:49 ` Manfred Spraul
2015-01-20 21:01 ` Stephen Smalley
2015-01-20 21:06 ` Eric Paris
2015-01-20 21:09 ` Stephen Smalley
2015-01-21 1:30 ` ethan zhao
2015-01-21 3:53 ` Ethan Zhao
2015-01-21 5:30 ` Manfred Spraul
2015-01-22 2:44 ` Ethan Zhao
2015-01-22 18:15 ` Manfred Spraul
2015-01-23 2:00 ` ethan zhao
2015-01-22 19:05 ` Stephen Smalley
2015-01-22 20:48 ` Davidlohr Bueso
2015-01-23 2:38 ` ethan zhao
2015-01-23 2:19 ` ethan zhao
2015-01-23 3:30 ` Davidlohr Bueso [this message]
2015-01-23 15:30 ` Ethan Zhao
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=1421983803.24914.3.camel@stgolabs.net \
--to=dave@stgolabs.net \
--cc=eparis@parisplace.org \
--cc=ethan.kernel@gmail.com \
--cc=ethan.kernel@gmail.conm \
--cc=ethan.zhao@oracle.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=stephen.smalley@gmail.com \
/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