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.) -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
