From: John Johansen <john.johansen@canonical.com>
To: James Morris <jmorris@namei.org>
Cc: SECURITY SUBSYSTEM <linux-security-module@vger.kernel.org>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: apparmor: two more regression fixes for 3.12
Date: Mon, 14 Oct 2013 11:37:22 -0700 [thread overview]
Message-ID: <525C39E2.4030507@canonical.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1310150220160.6053@tundra.namei.org>
On 10/14/2013 08:20 AM, James Morris wrote:
> On Sat, 12 Oct 2013, John Johansen wrote:
>
>> Hi James,
>>
>> Can you please pull and forward the following 2 fixes for regressions in
>> 3.12 apparmor
>>
sure replied below or you can pull them from the branch below which I just rebased
The following changes since commit d6099aeb4a9aad5e7ab1c72eb119ebd52dee0d52:
Merge branch 'fixes' of git://git.linaro.org/people/rmk/linux-arm (2013-10-14 10:02:23 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor for-security
for you to fetch changes up to 78aaf3232b29abbc83521814b946158b5c6293fc:
apparmor: fix bad lock balance when introspecting policy (2013-10-14 11:31:34 -0700)
----------------------------------------------------------------
John Johansen (2):
apparmor: fix memleak of the profile hash
apparmor: fix bad lock balance when introspecting policy
security/apparmor/apparmorfs.c | 4 +---
security/apparmor/policy.c | 1 +
2 files changed, 2 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2013-10-14 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <525906EE.90409@canonical.com>
2013-10-14 15:20 ` apparmor: two more regression fixes for 3.12 James Morris
2013-10-14 18:37 ` John Johansen [this message]
2013-10-14 18:44 ` [PATCH 1/2] apparmor: fix memleak of the profile hash John Johansen
2013-10-14 18:46 ` [PATCH 2/2] apparmor: fix bad lock balance when introspecting policy 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=525C39E2.4030507@canonical.com \
--to=john.johansen@canonical.com \
--cc=jmorris@namei.org \
--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