From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Parisc List <linux-parisc@vger.kernel.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Subject: [PATCH 1/3] fix missing TAINT_WARN problem
Date: Tue, 05 Jun 2012 13:52:03 +0900 [thread overview]
Message-ID: <1338871923.5176.9.camel@dabdike> (raw)
In-Reply-To: <1338871679.5176.7.camel@dabdike>
>From ad71a7070fd5912420c443b020c6cf796518f3e9 Mon Sep 17 00:00:00 2001
From: James Bottomley <James.Bottomley@HansenPartnership.com>
Date: Sun, 3 Jun 2012 01:49:32 -0700
Subject: fix missing TAINT_WARN problem
Al viro broke us with
commit edd63a2763bdae0daa4f0a4d4c5d61d1154352a5
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Fri Apr 27 13:42:45 2012 -0400
set_restore_sigmask() is never called without SIGPENDING (and never should be)
Although it's pretty much our fault since parisc's asm/bug.h uses
BUGWARN_TAINT but doesn't include the file that defines it. Fix that.
---
arch/parisc/include/asm/bug.h | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/parisc/include/asm/bug.h b/arch/parisc/include/asm/bug.h
index 72cfdb0..62a3333 100644
--- a/arch/parisc/include/asm/bug.h
+++ b/arch/parisc/include/asm/bug.h
@@ -1,6 +1,8 @@
#ifndef _PARISC_BUG_H
#define _PARISC_BUG_H
+#include <linux/kernel.h> /* for BUGFLAG_TAINT */
+
/*
* Tell the user there is some problem.
* The offending file and line are encoded in the __bug_table section.
--
1.7.4.1
next prev parent reply other threads:[~2012-06-05 4:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 4:47 [PATCH 0/3] fix recent parisc build breakages James Bottomley
2012-06-05 4:52 ` James Bottomley [this message]
2012-06-05 4:53 ` [PATCH 2/3] fix compile break in use of lib/strncopy_from_user.c James Bottomley
2012-06-05 4:54 ` [PATCH 3/3] fix code to find libgcc James Bottomley
2012-06-05 6:55 ` Sam Ravnborg
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=1338871923.5176.9.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-parisc@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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