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]
Message-ID: <53321D04.2040102@oracle.com>
Date:	Tue, 25 Mar 2014 20:19:16 -0400
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Alessandro Zummo <a.zummo@...ertech.it>
CC:	Tejun Heo <tj@...nel.org>, Greg KH <greg@...ah.com>,
	rtc-linux@...glegroups.com, LKML <linux-kernel@...r.kernel.org>
Subject: Re: kernfs/rtc: circular dependency between kernfs and ops_lock

On 03/25/2014 06:39 PM, Alessandro Zummo wrote:
> On Tue, 25 Mar 2014 17:52:30 -0400
> Sasha Levin <sasha.levin@...cle.com> wrote:
>
>>>
>>>    Pretty interesting indeed. One option would be to remove
>>>    the sys files before acquiring the lock. But I wonder
>>>    if this could lead to other issues.
>>>
>>
>> Ping? Seems this thing got lost.
>
>   What if we move
>
>     rtc_sysfs_del_device(rtc);
>
>   before acquiring the lock?

Trying it now, I'll leave it going for a week and see if it reproduces.


Thanks,
Sasha

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ