From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Eric Paris <eparis@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: flex_array related problems on selinux policy loading
Date: Mon, 31 Jan 2011 09:00:21 +0100 [thread overview]
Message-ID: <20110131080021.GI3070@secunet.com> (raw)
In-Reply-To: <1296147449.7567.5780.camel@nimitz>
On Thu, Jan 27, 2011 at 08:57:29AM -0800, Dave Hansen wrote:
> > >
> > > You have to check for and handle those allocation failures anyway.
> >
> > If we just return a pointer to the user that notifies that this was a
> > zerro size allocation, we would not need to allocate anything (like
> > kmalloc does), so we can't get allocation failures.
>
> Could you point me to some of this code? I'm having a hard time seeing
> how this is going to get used, and I don't see any use of
> ZERO_SIZE_PTR/ZERO_OR_NULL_PTR() outside of the sl*b code.
>
Perhaps I did not express it the right way, but
I did not say that this is used somewhere outside the sl*b code.
All I meant is that we return a pointer, like ZERO_SIZE_PTR
that notifies us that we have not allocated anything if a user
wants to access or to free data. This pointers are just for
internal usage of course.
Steffen
prev parent reply other threads:[~2011-01-31 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 12:26 flex_array related problems on selinux policy loading Steffen Klassert
2011-01-20 15:28 ` Dave Hansen
2011-01-21 7:20 ` Steffen Klassert
2011-01-21 15:57 ` Dave Hansen
2011-01-26 10:23 ` Steffen Klassert
2011-01-26 16:10 ` Dave Hansen
2011-01-27 12:15 ` Steffen Klassert
2011-01-31 8:08 ` Steffen Klassert
2011-01-26 13:04 ` Steffen Klassert
2011-01-26 16:15 ` Dave Hansen
2011-01-27 12:46 ` Steffen Klassert
2011-01-27 16:57 ` Dave Hansen
2011-01-31 8:00 ` Steffen Klassert [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=20110131080021.GI3070@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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 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.