linux-kernel - [tip:ia64/urgent] Fix sn_force_interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 30 Mar 2011 11:01:29 +0800
From:	"Alex,Shi" <alex.shi@...el.com>
To:	tony.luck@...el.com, tglx@...utronix.de,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc:	"Chen, Tim C" <tim.c.chen@...el.com>,
	"Shi, Alex" <alex.shi@...el.com>
Subject: [tip:ia64/urgent] Fix sn_force_interrupt_flag no defination issue

sn_force_interrupt_flag was removed in 39-rc1 patch. But it still be
used in arch/ia64/sn/kernel/sn2/sn_proc_fs.c. that make compilation
failed: 
arch/ia64/sn/built-in.o: In function `sn_force_interrupt_show':
sn_proc_fs.c:(.text+0xd281): undefined reference to `sn_force_interrupt_flag'
sn_proc_fs.c:(.text+0xd2a0): undefined reference to `sn_force_interrupt_flag'
A quick fix for this.

Signed-off-by: Alex Shi <alex.shi@...el.com>
---
 arch/ia64/sn/kernel/sn2/sn_proc_fs.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/ia64/sn/kernel/sn2/sn_proc_fs.c b/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
index c76d8dc..ce3215d 100644
--- a/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
+++ b/arch/ia64/sn/kernel/sn2/sn_proc_fs.c
@@ -51,7 +51,7 @@ static int licenseID_open(struct inode *inode, struct file *file)
  * the bridge chip.  The hardware will then send an interrupt message if the
  * interrupt line is active.  This mimics a level sensitive interrupt.
  */
-extern int sn_force_interrupt_flag;
+int sn_force_interrupt_flag;
 
 static int sn_force_interrupt_show(struct seq_file *s, void *p)
 {


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/