| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: deadlocks with fallocate |
| From: | Thomas Neumann <tneumann@xxxxxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 15 Oct 2009 01:16:27 +0200 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20091014150951.GA13123@xxxxxxxxxxxxx> |
| References: | <hak2l2$ko2$1@xxxxxxxxxxxxx> <20091014150951.GA13123@xxxxxxxxxxxxx> |
| User-agent: | KMail/1.12.2 (Linux/2.6.31-14-generic; KDE/4.3.2; x86_64; ; ) |
> And this thread is inside the fallocate handler. > > Can you try if the hack below makes the problem go away? > > + current->flags |= PF_FSTRANS; that seems to do the trick. I will test it some more, but so far it has already survived a workload that usually triggered the deadlock quite reliably. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Important: Email Account Verification Update!! !, Web Administrator |
|---|---|
| Next by Date: | Important: Email Account Verification Update!! !, Aminul Islam |
| Previous by Thread: | Re: deadlocks with fallocate, Christoph Hellwig |
| Next by Thread: | Re: deadlocks with fallocate, Thomas Neumann |
| Indexes: | [Date] [Thread] [Top] [All Lists] |