From: Andrew Morton <akpm@linux-foundation.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: John Keller <jpk@sgi.com>,
linux-kernel@vger.kernel.org, steiner@sgi.com,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH Resend] - SN: validate smp_affinity mask on intr
Date: Tue, 08 May 2007 19:19:45 +0000 [thread overview]
Message-ID: <20070508121945.3e8d29c1.akpm@linux-foundation.org> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A01719A90@scsmsx411.amr.corp.intel.com>
On Tue, 8 May 2007 11:03:20 -0700
"Luck, Tony" <tony.luck@intel.com> wrote:
> +#ifndef is_affinity_mask_valid
> +#define is_affinity_mask_valid() 1
> +#endif
> +
> int no_irq_affinity;
> static int irq_affinity_write_proc(struct file *file, const char __user *buffer,
> unsigned long count, void *data)
> @@ -42,6 +46,9 @@ static int irq_affinity_write_proc(struc
> if (err)
> return err;
>
> + if (!is_affinity_mask_valid(new_value))
> + return -EINVAL;
>
> This results in a warning:
> kernel/irq/proc.c:49: warning: implicit declaration of function `is_affinity_mask_valid'
>
It had a dopey little bug:
diff -puN kernel/irq/proc.c~sn-validate-smp_affinity-mask-on-intr-redirect-fix kernel/irq/proc.c
--- a/kernel/irq/proc.c~sn-validate-smp_affinity-mask-on-intr-redirect-fix
+++ a/kernel/irq/proc.c
@@ -28,7 +28,7 @@ static int irq_affinity_read_proc(char *
}
#ifndef is_affinity_mask_valid
-#define is_affinity_mask_valid() 1
+#define is_affinity_mask_valid(val) 1
#endif
int no_irq_affinity;
_
next prev parent reply other threads:[~2007-05-08 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 15:23 [PATCH Resend] - SN: validate smp_affinity mask on intr redirect John Keller
2007-05-08 18:03 ` Luck, Tony
2007-05-08 19:19 ` Andrew Morton [this message]
2007-05-08 20:14 ` Luck, Tony
2007-05-08 20:34 ` [PATCH Resend] - SN: validate smp_affinity mask on intr Andrew Morton
2007-05-08 22:14 ` John Keller
2007-05-08 23:01 ` [PATCH Resend] - SN: validate smp_affinity mask on intr redirect Peter Chubb
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=20070508121945.3e8d29c1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jpk@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tony.luck@intel.com \
/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