From: Milan Broz <mbroz@redhat.com>
To: Ritesh Raj Sarraf <rrs@researchut.com>
Cc: Alasdair G Kergon <agk@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Christophe Saout <christophe@saout.de>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
dm-crypt@saout.de
Subject: Re: [dm-devel] Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Sat, 01 Mar 2008 20:30:59 +0100 [thread overview]
Message-ID: <47C9AEF3.7040507@redhat.com> (raw)
In-Reply-To: <200803010029.18320.rrs@researchut.com>
Ritesh Raj Sarraf wrote:
> 1) Initialize a device using dm-crypt and LUKS
> 2) Create a filesystem on top of it and mount it.
> 3) Write huge amount of data (as a normal user). Something like 150GB.
>
> As the load goes hight (to something like 12-14), the kernel lock-up is logged
> into dmesg.
> At that moment, the OS is barely responsive.
>
>
Please could you try to reproduce it with this patch applied?
(patch for 2.6.25-rc3, for 2.6.24 will follow - code changed here)
Milan
mbroz@redhat.com
--
Add cond_resched() to prevent stuck in big bio processing.
Signed-off-by: Milan Broz <mbroz@redhat.com>
---
drivers/md/dm-crypt.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
index b04f98d..2032228 100644
--- a/drivers/md/dm-crypt.c
+++ b/drivers/md/dm-crypt.c
@@ -432,6 +432,7 @@ static int crypt_convert(struct crypt_config *cc,
/* fall through*/
case 0:
ctx->sector++;
+ cond_resched();
continue;
}
next prev parent reply other threads:[~2008-03-01 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 13:54 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt Ritesh Raj Sarraf
2008-02-29 7:20 ` Andrew Morton
2008-02-29 18:15 ` Herbert Xu
2008-02-29 18:46 ` [dm-devel] " Alasdair G Kergon
2008-02-29 18:59 ` Ritesh Raj Sarraf
2008-03-01 19:30 ` Milan Broz [this message]
2008-03-01 19:33 ` Milan Broz
2008-03-01 21:59 ` Gunter Ohrner
2008-03-02 7:58 ` Gunter Ohrner
2008-03-06 14:41 ` [dm-devel] " Ritesh Raj Sarraf
2008-06-02 3:07 ` Yan Li
2008-06-02 6:52 ` Milan Broz
2008-06-02 12:31 ` Yan Li
2008-06-02 12:51 ` Milan Broz
2008-06-05 22:44 ` Yan Li
2008-06-06 6:46 ` Milan Broz
[not found] ` <2f83bcba0806031246m30f92892wc868d81a9c29d680@mail.gmail.com>
2008-06-03 23:13 ` Yan Li
-- strict thread matches above, loose matches on Subject: below --
2008-03-01 15:44 [dm-devel] " Tomasz Chmielewski
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=47C9AEF3.7040507@redhat.com \
--to=mbroz@redhat.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=christophe@saout.de \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rrs@researchut.com \
/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