linux-kernel - Re: ia64: replace old cpumask functions with new one

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

Date:	Wed, 6 Jul 2011 14:14:58 -0700
From:	Tony Luck <tony.luck@...el.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	fenghua.yu@...el.com, linux-ia64@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: ia64: replace old cpumask functions with new one

2011/6/23 KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>:
> We plan to remove old obsolete cpumask functions and plan to
> change task->cpus_allowed implementation in future.
...
>  arch/ia64/kernel/smpboot.c              |   56 +++++++++++++++---------------

I get some new warnings in this file with your patch:


arch/ia64/kernel/smpboot.c:454: warning: passing argument 2 of
‘cpumask_set_cpu’ discards qualifiers from pointer target type
arch/ia64/kernel/smpboot.c:581: warning: passing argument 1 of
‘cpumask_clear’ discards qualifiers from pointer target type
arch/ia64/kernel/smpboot.c:613: warning: passing argument 2 of
‘cpumask_set_cpu’ discards qualifiers from pointer target type
arch/ia64/kernel/smpboot.c:637: warning: passing argument 2 of
‘cpumask_set_cpu’ discards qualifiers from pointer target type
arch/ia64/kernel/smpboot.c:745: warning: passing argument 2 of
‘cpumask_clear_cpu’ discards qualifiers from pointer target type

Four of the five involve "cpu_callin_mask" which is "volatile", the other is for
"cpu_present_mask" - not sure what the problem is for this one.

-Tony
--
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/