public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: David Howells <dhowells@redhat.com>
Cc: Chris Wright <chrisw@osdl.org>,
	linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] security/: possible cleanups
Date: Mon, 30 May 2005 21:41:31 +0200	[thread overview]
Message-ID: <20050530194131.GL10441@stusta.de> (raw)
In-Reply-To: <17465.1116338881@redhat.com>

On Tue, May 17, 2005 at 03:08:01PM +0100, David Howells wrote:
> Chris Wright <chrisw@osdl.org> wrote:
> 
> > I see no issue with the keys changes, except I'd rather see key_duplicate
> > removed entirely if it's not getting used.  David, is there a plan to
> > put it to use, or can Adrian remove it?
> 
> There was a keyctl call for it, I thought. I wonder what happened to it. Let
> me think about what I want to do with it. Note that if key_duplicate() gets
> removed, then the key_type->duplicate() op may as well be rooted out and shot
> too.

Have you thought about what to do with key_duplicate()?

> The rest of the patch looks vaguely okay.
> 
> David

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-05-30 19:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 18:45 [2.6 patch] security/: possible cleanups Adrian Bunk
2005-05-16 21:08 ` Chris Wright
2005-05-17 14:08   ` David Howells
2005-05-30 19:41     ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-31  0:33 Adrian Bunk
2005-11-07 21:18 Adrian Bunk

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=20050530194131.GL10441@stusta.de \
    --to=bunk@stusta.de \
    --cc=chrisw@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.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