From: Chris Wright <chrisw@sous-sol.org>
To: "Ahmed S. Darwish" <darwish.07@gmail.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
akpm <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH BUGFIX -rc5] Smack: Do not dereference NULL ipc object
Date: Wed, 19 Mar 2008 15:48:14 -0700 [thread overview]
Message-ID: <20080319224814.GC19346@sequoia.sous-sol.org> (raw)
In-Reply-To: <20080314231034.GA1701@ubuntu>
* Ahmed S. Darwish (darwish.07@gmail.com) wrote:
> In the SYSV ipc msgctl(),semctl(),shmctl() family, if the user passed
> *_INFO as the desired operation, no specific object is meant to be
> controlled and only system-wide information is returned. This leads
> to a NULL IPC object in the LSM hooks if the _INFO flag is given.
>
> Avoid dereferencing this NULL pointer in Smack ipc *ctl() methods.
Casey, this looks quite legit to me. Can you ack please.
thanks,
-chris
next prev parent reply other threads:[~2008-03-20 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 23:10 [PATCH BUGFIX -rc5] Smack: Do not dereference NULL ipc object Ahmed S. Darwish
2008-03-19 22:48 ` Chris Wright [this message]
2008-03-19 23:27 ` Casey Schaufler
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=20080319224814.GC19346@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=darwish.07@gmail.com \
--cc=linux-kernel@vger.kernel.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