From: James Morris <jmorris@namei.org>
To: John Johansen <john.johansen@canonical.com>
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: Tue, 15 Oct 2013 02:20:51 +1100 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1310150220160.6053@tundra.namei.org> (raw)
In-Reply-To: <525906EE.90409@canonical.com>
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
>
> thanks
> john
>
> ---
>
> The following changes since commit 94ecad0c9ca2c9345013d2417081cea7cf842c16:
>
> apparmor: fix suspicious RCU usage warning in policy.c/policy.h (2013-09-29 08:28:11 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor security-next
>
> for you to fetch changes up to dcb08d624b002693bed8ca6bf0456e09b4a90028:
>
> apparmor: fix bad lock balance when introspecting policy (2013-10-11 18:43:16 -0700)
>
> ----------------------------------------------------------------
> John Johansen (2):
> apparmor: fix memleak of the profile hash
> apparmor: fix bad lock balance when introspecting policy
>
Can you email me the patches? I need to apply them to current Linus.
--
James Morris
<jmorris@namei.org>
next parent reply other threads:[~2013-10-14 15:17 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 ` James Morris [this message]
2013-10-14 18:37 ` John Johansen
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=alpine.LRH.2.02.1310150220160.6053@tundra.namei.org \
--to=jmorris@namei.org \
--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
all inboxes | Powered by JetHome®