linux-kernel - Re: linux 4.1-rc7 deadlock

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: <CAKSJeFLb523beVQHqWhCtaBOECfeYrwWdojb5M8wqQWMfwJ72A@mail.gmail.com>
Date:	Tue, 9 Jun 2015 17:35:04 +0200
From:	Morten Stevens <mstevens@...oraproject.org>
To:	Daniel Wagner <wagi@...om.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: linux 4.1-rc7 deadlock

2015-06-09 16:10 GMT+02:00 Daniel Wagner <wagi@...om.org>:
> Hi Morten,

Hi Daniel,

> On 06/09/2015 01:54 PM, Morten Stevens wrote:
>> [   28.193327]  Possible unsafe locking scenario:
>>
>> [   28.194297]        CPU0                    CPU1
>> [   28.194774]        ----                    ----
>> [   28.195254]   lock(&mm->mmap_sem);
>> [   28.195709]                                lock(&xfs_dir_ilock_class);
>> [   28.196174]                                lock(&mm->mmap_sem);
>> [   28.196654]   lock(&isec->lock);
>> [   28.197108]
>
> [...]
>
>> Any ideas?
>
> I think you hit the same problem many have already reported:
>
> https://lkml.org/lkml/2015/3/30/594

Yes, that sounds very likely. But that was about 1 month ago, so I
thought that it has been fixed in the last weeks?

Best regards,

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