From: Andi Kleen <ak@muc.de>
To: "Stephen D. Smalley" <sds@epoch.ncsc.mil>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Changes to the LSM file-related hooks for 2.5.58
Date: 15 Jan 2003 09:49:48 +0100 [thread overview]
Message-ID: <m3fzrusspf.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <20030114191012$4fb6@gated-at.bofh.it>
"Stephen D. Smalley" <sds@epoch.ncsc.mil> writes:
>
> 3) Add a security_file_alloc call to init_private_file and create a
> release_private_file function to encapsulate release of private file
> structures. These changes ensure that security structures for private
> files will be allocated and freed appropriately.
Adding release_private_file requires fixing all code that uses
init_private_file (including possible third party code). Otherwise
you have some subtle leak. It would better to rename init_private_file to
some other name and add appropiate comments so that this can be catched
easily at compile time.
-Andi
next parent reply other threads:[~2003-01-15 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030114191012$4fb6@gated-at.bofh.it>
2003-01-15 8:49 ` Andi Kleen [this message]
2003-01-15 20:49 [RFC] Changes to the LSM file-related hooks for 2.5.58 Stephen D. Smalley
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 15:44 Stephen D. Smalley
2003-01-15 15:56 ` Christoph Hellwig
2003-01-15 16:04 ` Christoph Hellwig
2003-01-14 19:08 Stephen D. Smalley
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=m3fzrusspf.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
/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;
as well as URLs for NNTP newsgroup(s).