linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: John Johansen <john.johansen@canonical.com>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH 2/4] AppArmor: Fix security_task_setrlimit logic for 2.6.36 changes
Date: Mon, 30 Aug 2010 23:33:01 +0200	[thread overview]
Message-ID: <4C7C238D.2070505@gmail.com> (raw)
In-Reply-To: <4C7BE205.40202@canonical.com>

On 08/30/2010 06:53 PM, John Johansen wrote:
> /* TODO: extend resource control to handle other (non current) processes.
>  * AppArmor rules currently have the implicit assumption that the task
>  * is setting the resource of the current process
>  */

Makes sense(TM) now.

thanks,
-- 
js

  reply	other threads:[~2010-08-30 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28  1:33 [Patch 0/4] AppArmor post 2.6.36 merge fixups John Johansen
2010-08-28  1:33 ` [PATCH 1/4] AppArmor: Drop hack to remove appended " (deleted)" string John Johansen
2010-08-28  1:33 ` [PATCH 2/4] AppArmor: Fix security_task_setrlimit logic for 2.6.36 changes John Johansen
2010-08-28 17:10   ` John Johansen
2010-08-28 18:15     ` Jiri Slaby
2010-08-28 20:35       ` John Johansen
2010-08-28 20:48         ` Jiri Slaby
2010-08-30 16:53           ` John Johansen
2010-08-30 21:33             ` Jiri Slaby [this message]
2010-09-06 17:10               ` John Johansen
2010-08-28  1:33 ` [PATCH 3/4] AppArmor: Fix splitting an fqname into separate namespace and profile names John Johansen
2010-08-28  1:33 ` [PATCH 4/4] AppArmor: Fix locking from removal of profile namespace John Johansen

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=4C7C238D.2070505@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=john.johansen@canonical.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 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).