From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 108631] Stuck on mb_cache_spinlock
Date: Thu, 07 Jan 2016 15:33:08 +0000 [thread overview]
Message-ID: <bug-108631-13602-IXzpZRjmsF@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-108631-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=108631
--- Comment #5 from Norman Meilick <nm@sbe.de> ---
Thank you very much, I'll try the patches tomorrow.
And yes, we're indeed running several LXC containers on the affected servers.
One quick correction to my original comment: When I stated that kernel 3.14
does not seem to be affected, I mixed up the version number. It's 3.13 that
doesn't exhibit any problems for us (we didn't test with 3.14). I'm sorry for
the mistake.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-01-07 15:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 16:36 [Bug 108631] New: Stuck on mb_cache_spinlock bugzilla-daemon
2016-01-07 9:02 ` [Bug 108631] " bugzilla-daemon
2016-01-07 14:09 ` bugzilla-daemon
2016-01-07 14:10 ` bugzilla-daemon
2016-01-07 15:06 ` bugzilla-daemon
2016-01-07 15:33 ` bugzilla-daemon [this message]
2016-01-07 15:49 ` bugzilla-daemon
2016-01-22 9:08 ` bugzilla-daemon
2016-03-20 21:54 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108631-13602-IXzpZRjmsF@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).