Bug 10378
Summary: | Task blocked for more than 120 seconds | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Ritesh Raj Sarraf (linux-kernel-bugs) |
Component: | LVM2/DM | Assignee: | Alasdair G Kergon (agk) |
Status: | CLOSED CODE_FIX | ||
Severity: | high | CC: | neilb |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.24, 2.6.25-rc6 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Ritesh Raj Sarraf
2008-04-01 22:30:56 UTC
There's a commit in between rc6..rc8 which I believe addresses this bug. Neil, Since you run RC kernels, will it be possible for you to test rc8 ? commit 3f1e9070f63b0eecadfa059959bf7c9dbe835962 Author: Milan Broz <mbroz@redhat.com> Date: Fri Mar 28 14:16:07 2008 -0700 dm crypt: fix ctx pending Fix regression in dm-crypt introduced in commit 3a7f6c990ad04e6f576a159876c602d14d6f7fef ("dm crypt: use async crypto"). If write requests need to be split into pieces, the code must not process them in parallel because the crypto context cannot be shared. So there can be parallel crypto operations on one part of the write, but only one write bio can be processed at a time. This is not optimal and the workqueue code needs to be optimized for parallel processing, but for now it solves the problem without affecting the performance of synchronous crypto operation (most of current dm-crypt users). http://bugzilla.kernel.org/show_bug.cgi?id=10242 http://bugzilla.kernel.org/show_bug.cgi?id=10207 Signed-off-by: Milan Broz <mbroz@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com> Cc: "Rafael J. Wysocki" <rjw@sisk.pl> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Neil, Did you get a chance to verify it with the latest rc? Sorry, but I've got no idea what comment #2 is asking. I'm not aware that I was going to verify anything.... Confused. You posted the same behavior on dm-devel some weeks back. This behavior was seen by me too. That is why I opened the bugzilla. Since you mentioned that you did use rc kernels, I wanted to know if the behavior was still present after the above mentioned patch was applied. I asked for your help in comment #1 I think I know what caused the confusion. Samuel Tardieu has this problem and sent and email to the linux-raid mailing list. I forwarded it to dm-devel because that was a more appropriate mailing list. You misunderstood that email and thought I was experiencing the problem. But I wasn't. I've never used dm-crypt. You need to talk to Samuel. Assuming this is fixed. If not, please reopen with an updated trace from a recent kernel. |