All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Wesley Leggette <wleggette@kaylix.net>
Cc: linux-kernel@vger.kernel.org, Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: Kernel panic in kcryptd
Date: Thu, 30 Oct 2008 19:30:22 +0100	[thread overview]
Message-ID: <4909FD3E.8070104@redhat.com> (raw)
In-Reply-To: <C56C1A70-4E26-4D12-A1BC-4E744BCD51C5@kaylix.net>


Wesley Leggette wrote:
> When performing large IO, seemingly only when over the network, I  
> receive a kernel panic that seems to be happening in the kcryptd module.
> 
> Here's two scenarios I've encountered this:
> 
> ietd -> kcryptd -> mdadm raid6

iscsi over dm crypt over mdadm?
And I see snapshots in the log too, isn't there snapshot under
the crypt mapping?

Is it reproducible without snapshots involved?

Maybe it is related to recently fixed problem there...
I think these patches solves the snapshot crashes (cc Mikulas)

http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/2.6.27/dm-snapshot-fix-primary_pe-race.patch
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-snapshot-wait-for-chunks-in-destructor.patch

Milan

> Linux version 2.6.26-bpo.1-686-bigmem (Debian 2.6.26-4~bpo40+1) (nobse@debian.org 
> ) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP  
> Tue Sep 2 18:42:50 UTC 2008
> 
> 
> 
> Oct 29 04:55:15 fargo kernel: [4285317.219492] ------------[ cut  
> here ]------------
> Oct 29 04:55:15 fargo kernel: [4285317.219492] kernel BUG at mm/slab.c: 
> 3008!
> Oct 29 04:55:15 fargo kernel: [4285317.219492] invalid opcode: 0000  
> [#1] SMP
> Oct 29 04:55:15 fargo kernel: [4285317.219492] Modules linked in:  
> usb_storage iscsi_trgt crc32c libcrc32c ipv6 ib_iser
>   rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi  
> scsi_transport_iscsi ac battery xt_tcpudp nf_conn
> track_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables  
> ext3 jbd mbcache loop snd_hda_intel i2c_i801 i2c_co
> re snd_pcm snd_timer snd soundcore iTCO_wdt intel_agp agpgart button  
> snd_page_alloc parport_pc parport evdev pcspkr fl
> oppy reiserfs sha256_generic aes_i586 aes_generic cbc dm_crypt  
> crypto_blkcipher dm_mirror dm_log dm_snapshot dm_mod ra
> id456 async_xor async_memcpy async_tx xor raid1 md_mod ide_generic  
> jmicron ide_core sd_mod sata_promise ata_generic ah
> ci r8169 libata scsi_mod uhci_hcd dock ehci_hcd usbcore thermal  
> processor fan thermal_sys [last unloaded: libcrc32c]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]
> Oct 29 04:55:15 fargo kernel: [4285317.219492] Pid: 4191, comm:  
> kcryptd Not tainted (2.6.26-bpo.1-686-bigmem #1)
> Oct 29 04:55:15 fargo kernel: [4285317.219492] EIP: 0060:[<c017b8e8>]  
> EFLAGS: 00010046 CPU: 0
> Oct 29 04:55:15 fargo kernel: [4285317.219492] EIP is at  
> cache_alloc_refill+0xeb/0x48b
> Oct 29 04:55:15 fargo kernel: [4285317.219492] EAX: 0000003b EBX:  
> 00000012 ECX: f6d4d1c0 EDX: df32c000
> Oct 29 04:55:15 fargo kernel: [4285317.219492] ESI: c0878000 EDI:  
> 00000012 EBP: f540cac0 ESP: e70b5d78
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  DS: 007b ES: 007b FS:  
> 00d8 GS: 0000 SS: 0068
> Oct 29 04:55:15 fargo kernel: [4285317.219492] Process kcryptd (pid:  
> 4191, ti=e70b4000 task=f696ba00 task.ti=e70b4000)
> Oct 29 04:55:15 fargo kernel: [4285317.219492] Stack: 00000000  
> 0000003b 00011200 f6d4d1c0 f5443e00 00000000 c0136139 f
> 51011ec
> Oct 29 04:55:15 fargo kernel: [4285317.219492]        e70b5de8  
> 00000202 c0136194 00000000 f6d4d1c0 00000206 00011200 c
> 017b7b6
> Oct 29 04:55:15 fargo kernel: [4285317.219492]        00000000  
> f540ca80 00000000 00011210 c015f909 f8935be2 df32c4c8 f
> 6430e40
> Oct 29 04:55:15 fargo kernel: [4285317.219492] Call Trace:
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c0136139>]  
> __queue_work+0x1c/0x28
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c0136194>] queue_work 
> +0x33/0x3c
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c017b7b6>]  
> kmem_cache_alloc+0x47/0x8e
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c015f909>]  
> mempool_alloc+0x1c/0xba
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f8935be2>]  
> copy_callback+0x0/0x2c [dm_snapshot]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f893533e>]  
> __find_pending_exception+0x62/0x122 [dm_snapshot]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f89355c1>] origin_map 
> +0x105/0x23f [dm_snapshot]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f89064e2>] __map_bio 
> +0x4d/0x12a [dm_mod]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f8906309>] clone_bio 
> +0x3f/0x6f [dm_mod]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f8906ff1>]  
> __split_bio+0x156/0x3f7 [dm_mod]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f896e33f>]  
> crypto_cbc_encrypt+0x12b/0x13f [cbc]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f894d6d8>]  
> aes_encrypt+0x0/0xc [aes_i586]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f89076ff>] dm_request 
> +0xd3/0xf2 [dm_mod]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c01dc365>]  
> generic_make_request+0x34d/0x37b
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f89488a9>]  
> crypt_convert+0x20f/0x240 [dm_crypt]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f8948a98>]  
> kcryptd_crypt+0x1be/0x267 [dm_crypt]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<f89488da>]  
> kcryptd_crypt+0x0/0x267 [dm_crypt]
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c0135d32>]  
> run_workqueue+0x74/0xf2
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c013640d>]  
> worker_thread+0x0/0xbd
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c01364c0>]  
> worker_thread+0xb3/0xbd
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c01386ac>]  
> autoremove_wake_function+0x0/0x2d
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c01385eb>] kthread 
> +0x38/0x5d
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c01385b3>] kthread 
> +0x0/0x5d
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  [<c01094ff>]  
> kernel_thread_helper+0x7/0x10
> Oct 29 04:55:15 fargo kernel: [4285317.219492]  =======================
> Oct 29 04:55:15 fargo kernel: [4285317.219492] Code: 8b 75 00 39 ee 75  
> 15 8b 75 10 8d 45 10 c7 45 34 01 00 00 00 39 c6
>   0f 84 a5 00 00 00 8b 4c 24 0c 8b 81 98 00 00 00 39 46 10 72 37 <0f>  
> 0b eb fe 8b 44 24 10 8b 5e 14 8b 08 8b 44 24 0c 8
> b 90 8c 00
> Oct 29 04:55:15 fargo kernel: [4285317.219492] EIP: [<c017b8e8>]  
> cache_alloc_refill+0xeb/0x48b SS:ESP 0068:e70b5d78
> Oct 29 04:55:15 fargo kernel: [4285317.219492] ---[ end trace  
> 0bb16d783d7c2616 ]---

  reply	other threads:[~2008-10-30 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 16:02 Kernel panic in kcryptd Wesley Leggette
2008-10-30 18:30 ` Milan Broz [this message]
2008-10-30 18:34   ` Wesley Leggette
2008-10-30 18:37     ` Wesley Leggette
2008-10-30 19:04       ` Milan Broz

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=4909FD3E.8070104@redhat.com \
    --to=mbroz@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=wleggette@kaylix.net \
    /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.