linux-kernel - Re: [PATCH 0/3] smp: reduce stack requirements for smp_call_function

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>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080908.134805.45081035.davem@davemloft.net>
Date:	Mon, 08 Sep 2008 13:48:05 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	travis@....com
Cc:	nickpiggin@...oo.com.au, mingo@...e.hu, akpm@...ux-foundation.org,
	steiner@....com, jes@....com, tglx@...utronix.de,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] smp: reduce stack requirements for
 smp_call_function_mask

From: Mike Travis <travis@....com>
Date: Mon, 08 Sep 2008 13:11:59 -0700

> I was wondering if we'd need to be able to default a cpumask_t pointer
> argument to be a const and then use a different method for those cases
> where it shouldn't be?  This would strengthen the compiler type checking
> of functions calls.

Yes, of course, the pointer should be const.
--
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/