All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 44731] ext4 deadlock under heavy io?
Date: Wed, 29 Aug 2012 16:38:24 +0000 (UTC)	[thread overview]
Message-ID: <20120829163824.38B6B11FB38@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-44731-13602@https.bugzilla.kernel.org/>

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





--- Comment #8 from Mirek Rusin <mirek@me.com>  2012-08-29 16:38:23 ---
Nick, yes it does - for software raid, right?

I'm using hardware raid.

This code is not even loaded into kernel (I've got it in kernel config as
(m)odule, and it doesn't appear in /proc/modules - this code is not used at all
in my case).

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-08-29 16:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 12:23 [Bug 44731] New: ext4 deadlock under heavy io? bugzilla-daemon
2012-07-13 14:01 ` [Bug 44731] " bugzilla-daemon
2012-07-13 14:06 ` bugzilla-daemon
2012-07-16 20:54 ` bugzilla-daemon
2012-08-29 14:23 ` bugzilla-daemon
2012-08-29 15:09 ` bugzilla-daemon
2012-08-29 15:50 ` bugzilla-daemon
2012-08-29 16:07 ` bugzilla-daemon
2012-08-29 16:12 ` bugzilla-daemon
2012-08-29 16:38 ` bugzilla-daemon [this message]
2012-08-29 17:26 ` bugzilla-daemon
2012-08-30  8:18 ` bugzilla-daemon
2012-08-30  9:06 ` bugzilla-daemon
2012-08-30  9:41 ` bugzilla-daemon
2012-08-30 13:34 ` bugzilla-daemon
2012-08-31  9:23 ` bugzilla-daemon
2012-08-31 13:03 ` bugzilla-daemon
2012-09-03 10:24 ` bugzilla-daemon
2012-10-24 20:38 ` bugzilla-daemon
2013-11-20  0:04 ` 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=20120829163824.38B6B11FB38@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.