linux-kernel - hwmon: coretemp: use dynamically allocated array to store per core data

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

Message-Id: <1441979810-22810-1-git-send-email-lukasz.odzioba@intel.com>
Date:	Fri, 11 Sep 2015 15:56:49 +0200
From:	Lukasz Odzioba <lukasz.odzioba@...el.com>
To:	fenghua.yu@...el.com
Cc:	jdelvare@...e.de, linux@...ck-us.net, lm-sensors@...sensors.org,
	linux-kernel@...r.kernel.org
Subject: hwmon: coretemp: use dynamically allocated array to store per core data 

This patch is continuation of my previous work. After Guenter Roeck's and Jean Delware's comments I changed list to an array. Initial array size is 4 and it is extended when core id exeeds size of the array, which in practice can mean every time a new core is initialized. I am not sure whether it is reasonable since it implies a lot of krealloc calls with small size increments. Please let me know if you think that more greedy approach would be better here. 

Comments are welcome.

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