linux-ext4 - [Bug 108631] Stuck on mb_cache

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-108631-13602-b4J1IdDOmm@https.bugzilla.kernel.org/>
Date:	Fri, 22 Jan 2016 09:08:18 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 108631] Stuck on mb_cache_spinlock

https://bugzilla.kernel.org/show_bug.cgi?id=108631

--- Comment #7 from Norman Meilick <nm@....de> ---
I'm sorry for the long delay, testing took longer than expected. While we could
trigger the problem every time with kernels 3.14 to 3.18, it took 2-3 attempts
(usually about 8 hours of backing up around 2.5M files) until the spinlock
contention appeared with kernels 4.2.0 and 4.4.0-rc8.

Since applying Jan's patches to 4.4.0-rc8 we have not experienced any problems,
so it seems to us that this fixed the issue. Thank you very much to both of
you.

I'm also grateful for the advice regarding containers. On our test server we
only have six containers with a modest memory use (we made sure to monitor it
during the tests), so this likely wasn't an issue there.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html