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]
Date:	Mon, 30 May 2016 23:13:47 -0700
From:	Eduardo Valentin <edubezval@...il.com>
To:	Keerthy <a0393675@...com>
Cc:	Rui Zhang <rui.zhang@...el.com>,
	Linux PM <linux-pm@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv3 00/48] thermal: reorganizing thermal core

On Tue, May 31, 2016 at 09:54:08AM +0530, Keerthy wrote:
> Hi Eduardo,
> 
> On Tuesday 31 May 2016 03:45 AM, Eduardo Valentin wrote:
> >Folks,
> >
> >This is V3 of a patch series to improve thermal core. The idea
> >here is to reorganize the code and improve the way we
> >handle sysfs entries.
> >
> >The change in behavior is that now, thermal zones with empty
> >.type will not be allowed to be registered. Also, the way
> >we handle scanf's return code is now checking for
> >number of successful inputs.
> >
> >After this series, thermal core is split into the following files:
> >- thermal_sysfs.c: contains the functions handling the sysfs nodes
> >- thermal_helpers.c: groups functions that do not need to touch thermal
> >core internal data structures, such as internal lists, and list locks.
> >- thermal_core.c: functions to handle the lifecycle of the subsystem,
> >its governors, cooling devices, thermal zone devices, and their
> >interactions.
> >
> >I don't expect any impact on userspace.
> >
> 
> I applied the whole 48 patch series on top of mainline kernel.
> 
> I see boot crash when i have thermal modules built in kernel for dra7/dra72
> boards.
> 
> dra7 bootlog: http://pastebin.ubuntu.com/16859184/

I will be sending a v4 soon. I will also push to a branch.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ