From: Milan Broz <mbroz@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
just.for.lkml@googlemail.com, hch@infradead.org,
herbert@gondor.hengli.com.au, Tejun Heo <tj@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 2.6.36-rc7
Date: Thu, 07 Oct 2010 22:13:00 +0200 [thread overview]
Message-ID: <4CAE29CC.8030702@redhat.com> (raw)
In-Reply-To: <4CAE1F47.3050105@kernel.org>
On 10/07/2010 09:28 PM, Tejun Heo wrote:
> I'm afraid there is a possibly workqueue related deadlock under high
> memory pressure. It happens on dm-crypt + md raid1 configuration.
> I'm not yet sure whether this is caused by workqueue failing to kick
> rescuers under memory pressure or the shared workqueue is making an
> already existing problem more visible and in the process of setting up
> an environment to reproduce the problem.
>
> http://thread.gmane.org/gmane.comp.file-systems.xfs.general/34922/focus=1044784
Yes, XFS is very good to show up problems in dm-crypt:)
But there was no change in dm-crypt which can itself cause such problem,
planned workqueue changes are not in 2.6.36 yet.
Code is basically the same for the last few releases.
So it seems that workqueue processing really changed here under memory pressure.
Milan
p.s.
Anyway, if you are able to reproduce it and you think that there is problem
in per-device dm-crypt workqueue, there are patches from Andi for shared
per-cpu workqueue, maybe it can help here. (But this is really not RC material.)
Unfortunately not yet in dm-devel tree, but I have them here ready for review:
http://mbroz.fedorapeople.org/dm-crypt/2.6.36-devel/
(all 4 patches must be applied, I hope Alasdair will put them in dm quilt soon.)
next prev parent reply other threads:[~2010-10-07 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=LsBNU+O2hqZUcM2nYM_ze6qPq3thwSZBMtY_v@mail.gmail.com>
2010-10-07 19:28 ` Linux 2.6.36-rc7 Tejun Heo
2010-10-07 20:13 ` Milan Broz [this message]
2010-10-08 17:02 ` [dm-devel] " Tejun Heo
2010-10-10 11:56 ` Torsten Kaiser
2010-10-11 10:09 ` [PATCH wq#for-next] workqueue: fix HIGHPRI handling in keep_working() Tejun Heo
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=4CAE29CC.8030702@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=herbert@gondor.hengli.com.au \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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).