All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Yan Li <elliot.li.tech@gmail.com>
Cc: Ritesh Raj Sarraf <rrs@researchut.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	dm-crypt@saout.de, linux-kernel@vger.kernel.org,
	dm-devel@redhat.com, rjmaomao@gmail.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Alasdair G Kergon <agk@redhat.com>,
	Christophe Saout <christophe@saout.de>
Subject: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Mon, 02 Jun 2008 08:52:00 +0200	[thread overview]
Message-ID: <48439890.6030904@redhat.com> (raw)
In-Reply-To: <20080602030738.GA7761@yantp.cn.ibm.com>


Yan Li wrote:
> On Thu, 28 Feb 2008 23:20:48 -0800, Andrew Morton wrote:
>> On Thu, 28 Feb 2008 19:24:03 +0530 Ritesh Raj Sarraf <rrs@researchut.com> wrote:
>>> I noted kernel soft lockup messages on my laptop when doing a lot of I/O 
>>> (200GB) to a dm-crypt device. It was setup using LUKS.
>>> The I/O never got disrupted nor anything failed. Just the messages.
> 
> I met the same problem yesterday.
> 
>> Could be a dm-crypt problem, could be a crypto problem, could even be a
>> core block problems.
> 
> I think it's due to heavy encryption computation that run longer than
> 10s and triggered the warning. By heavy I mean dm-crypt with
> aes-xts-plain, 512b key size.
> 
> This is a typical soft lockup call trace snip from dmesg:
> Call Trace:
>  [<ffffffff882c60b6>] :xts:crypt+0x9d/0xea
>  [<ffffffff882b5705>] :aes_x86_64:aes_encrypt+0x0/0x5
>  [<ffffffff882b5705>] :aes_x86_64:aes_encrypt+0x0/0x5
>  [<ffffffff882c622e>] :xts:encrypt+0x41/0x46
>  [<ffffffff8828273f>] :dm_crypt:crypt_convert_scatterlist+0x7b/0xc7
>  [<ffffffff882828ae>] :dm_crypt:crypt_convert+0x123/0x15d
>  [<ffffffff88282abd>] :dm_crypt:kcryptd_do_crypt+0x1d5/0x253
>  [<ffffffff882828e8>] :dm_crypt:kcryptd_do_crypt+0x0/0x253
>  [<ffffffff802448e5>] run_workqueue+0x7f/0x10b
> ... (omitted)

Please could you try if  patch here helps and doesn't cause performance degradation?

http://www2.kernel.org/pub/linux/kernel/people/agk/patches/2.6/2.6.25/dm-crypt-add-cond_resched.patch

...
> Anybody see a data corruption?

It shouldn't cause any corruption of data.

Milan

WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <mbroz@redhat.com>
To: Yan Li <elliot.li.tech@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ritesh Raj Sarraf <rrs@researchut.com>,
	Christophe Saout <christophe@saout.de>,
	linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	Herbert Xu <herbert@gondor.apana.org.au>,
	rjmaomao@gmail.com, Alasdair G Kergon <agk@redhat.com>,
	dm-crypt@saout.de
Subject: Re: 2.6.24 Kernel Soft Lock Up with heavy I/O in dm-crypt
Date: Mon, 02 Jun 2008 08:52:00 +0200	[thread overview]
Message-ID: <48439890.6030904@redhat.com> (raw)
In-Reply-To: <20080602030738.GA7761@yantp.cn.ibm.com>


Yan Li wrote:
> On Thu, 28 Feb 2008 23:20:48 -0800, Andrew Morton wrote:
>> On Thu, 28 Feb 2008 19:24:03 +0530 Ritesh Raj Sarraf <rrs@researchut.com> wrote:
>>> I noted kernel soft lockup messages on my laptop when doing a lot of I/O 
>>> (200GB) to a dm-crypt device. It was setup using LUKS.
>>> The I/O never got disrupted nor anything failed. Just the messages.
> 
> I met the same problem yesterday.
> 
>> Could be a dm-crypt problem, could be a crypto problem, could even be a
>> core block problems.
> 
> I think it's due to heavy encryption computation that run longer than
> 10s and triggered the warning. By heavy I mean dm-crypt with
> aes-xts-plain, 512b key size.
> 
> This is a typical soft lockup call trace snip from dmesg:
> Call Trace:
>  [<ffffffff882c60b6>] :xts:crypt+0x9d/0xea
>  [<ffffffff882b5705>] :aes_x86_64:aes_encrypt+0x0/0x5
>  [<ffffffff882b5705>] :aes_x86_64:aes_encrypt+0x0/0x5
>  [<ffffffff882c622e>] :xts:encrypt+0x41/0x46
>  [<ffffffff8828273f>] :dm_crypt:crypt_convert_scatterlist+0x7b/0xc7
>  [<ffffffff882828ae>] :dm_crypt:crypt_convert+0x123/0x15d
>  [<ffffffff88282abd>] :dm_crypt:kcryptd_do_crypt+0x1d5/0x253
>  [<ffffffff882828e8>] :dm_crypt:kcryptd_do_crypt+0x0/0x253
>  [<ffffffff802448e5>] run_workqueue+0x7f/0x10b
> ... (omitted)

Please could you try if  patch here helps and doesn't cause performance degradation?

http://www2.kernel.org/pub/linux/kernel/people/agk/patches/2.6/2.6.25/dm-crypt-add-cond_resched.patch

...
> Anybody see a data corruption?

It shouldn't cause any corruption of data.

Milan

  reply	other threads:[~2008-06-02  6:52 UTC|newest]

Thread overview: 30+ 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  7:20   ` Andrew Morton
2008-02-29 18:15   ` Herbert Xu
2008-02-29 18:15     ` Herbert Xu
2008-02-29 18:46   ` Alasdair G Kergon
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
2008-03-01 19:30         ` [dm-devel] " Milan Broz
2008-03-01 19:33         ` Milan Broz
2008-03-01 19:33           ` [dm-devel] " Milan Broz
2008-03-01 21:59           ` Gunter Ohrner
2008-03-01 21:59             ` Gunter Ohrner
2008-03-02  7:58             ` Gunter Ohrner
2008-03-02  7:58               ` Gunter Ohrner
2008-03-06 14:41           ` Ritesh Raj Sarraf
2008-03-06 14:41             ` [dm-devel] " Ritesh Raj Sarraf
2008-06-02  3:07   ` Yan Li
2008-06-02  6:52     ` Milan Broz [this message]
2008-06-02  6:52       ` Milan Broz
2008-06-02 12:31       ` Yan Li
2008-06-02 12:51         ` Milan Broz
2008-06-02 12:51           ` Milan Broz
2008-06-05 22:44           ` Yan Li
2008-06-05 22:44             ` Yan Li
2008-06-06  6:46             ` Milan Broz
2008-06-06  6:46               ` Milan Broz
2008-06-03 19:46         ` Ritesh Raj Sarraf
2008-06-03 23:13           ` Yan Li

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=48439890.6030904@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=elliot.li.tech@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjmaomao@gmail.com \
    --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 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.