From: John Johansen <john.johansen@canonical.com>
To: Chaitanya <chaitanyatk@posedge.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] Apparamor: Fix the OOPS due to wrong header inclusion in file in Makefile(3.7.0-rc1 Kernel)
Date: Mon, 17 Dec 2012 04:47:33 -0800 [thread overview]
Message-ID: <50CF1465.3050205@canonical.com> (raw)
In-Reply-To: <50CF0C21.60101@posedge.com>
On 12/17/2012 04:12 AM, Chaitanya wrote:
>
>
> Fix the OOPS in the apparmor security module
> during the bootup.(oops points to strlen in audit_log_untrustedstring function)
> Note: Actual fix lifted from Al-Viro.
>
> Signed-off-by: Chaitanya T K <chaitanyatk@posedge.com>
thanks for reporting, this patch was included in 3.7-rc2
see 43c422eda99b894f18d1cca17bcd2401efaf7bd0
> ---
> security/apparmor/Makefile | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/security/apparmor/Makefile b/security/apparmor/Makefile
> index 7b3021c..5706b74 100644
> --- a/security/apparmor/Makefile
> +++ b/security/apparmor/Makefile
> @@ -57,7 +57,7 @@ cmd_make-rlim = echo "static const char *const rlim_names[RLIM_NLIMITS] = {" \
>
> $(obj)/capability.o : $(obj)/capability_names.h
> $(obj)/resource.o : $(obj)/rlim_names.h
> -$(obj)/capability_names.h : $(srctree)/include/linux/capability.h \
> +$(obj)/capability_names.h : $(srctree)/include/uapi/linux/capability.h \
> $(src)/Makefile
> $(call cmd,make-caps)
> $(obj)/rlim_names.h : $(srctree)/include/uapi/asm-generic/resource.h \
>
>
>
>
next prev parent reply other threads:[~2012-12-17 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201212171158.qBHBwYni003158@chaitanya-desktop>
2012-12-17 12:12 ` [PATCH] Apparamor: Fix the OOPS due to wrong header inclusion in file in Makefile(3.7.0-rc1 Kernel) Chaitanya
2012-12-17 12:47 ` John Johansen [this message]
2012-12-17 15:17 ` Krishna Chaitanya
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=50CF1465.3050205@canonical.com \
--to=john.johansen@canonical.com \
--cc=chaitanyatk@posedge.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).