linux-kernel - RE: [PATCH] infiniband, ipath: convert old cpumask api into 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] [day] [month] [year] [list]

Message-ID: <35AAF1E4A771E142979F27B51793A4888838CD0EDE@AVEXMB1.qlogic.org>
Date:	Tue, 31 May 2011 14:10:04 -0700
From:	Mike Marciniszyn <mike.marciniszyn@...gic.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	"roland@...nel.org" <roland@...nel.org>,
	"sean.hefty@...el.com" <sean.hefty@...el.com>,
	"hal.rosenstock@...il.com" <hal.rosenstock@...il.com>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
	Dept_Infinipath <Dept_Infinipath@...gic.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] infiniband, ipath: convert old cpumask api into new one

> Subject: [PATCH] infiniband, ipath: convert old cpumask api into new
> one
>
> Adapt new api. we plan to remove old one later. Almost change are
> trivial. but there is one real fix. following code is unsafe.
>
>       int ncpus = num_online_cpus()
>       for (i = 0; i < ncpus; i++) {
>               ..
>       }
>

Thanks for the patch!

Acked-by: Mike Marciniszyn <mike.marciniszyn@...gic.com>

This message and any attached documents contain information from QLogic Corporation or its wholly-owned subsidiaries that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.

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