mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Daniel Kobras <kobras@linux.de>,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] Re: [PATCH] dm: Fix deadlock under high i/o load in raid1 setup.
Date: Mon, 14 Aug 2006 16:05:09 +0100	[thread overview]
Message-ID: <20060814150509.GO18633@agk.surrey.redhat.com> (raw)
In-Reply-To: <20060812130228.f7954b5f.akpm@osdl.org>

On Sat, Aug 12, 2006 at 01:02:28PM -0700, Andrew Morton wrote:
> Alasdair, I'd say that this is a 2.6.18 fix and a 2.6.17.x backport.
 
Yes.

> Or move the mempool_free()ing out of kmorrord context and into
> IO-completion context, perhaps.

That's how some other dm targets handle this particular problem.
 
Alasdair
-- 
agk@redhat.com

      reply	other threads:[~2006-08-14 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 16:44 Daniel Kobras
2006-08-12 20:02 ` Andrew Morton
2006-08-14 15:05   ` Alasdair G Kergon [this message]

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=20060814150509.GO18633@agk.surrey.redhat.com \
    --to=agk@redhat.com \
    --cc=akpm@osdl.org \
    --cc=dm-devel@redhat.com \
    --cc=kobras@linux.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®