From: Christoph Hellwig <hch@infradead.org>
To: Thomas Neumann <tneumann@users.sourceforge.net>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@oss.sgi.com
Subject: Re: deadlocks with fallocate
Date: Thu, 15 Oct 2009 08:13:45 -0400 [thread overview]
Message-ID: <20091015121345.GA18234@infradead.org> (raw)
In-Reply-To: <200910150758.06003.tneumann@users.sourceforge.net>
On Thu, Oct 15, 2009 at 07:58:05AM +0200, Thomas Neumann wrote:
> I did some more tests, and indeed the patch makes the deadlock go away. Your
> description of it as a hack makes me somewhat concerned about using it
> permanently, but hopefully you will find a proper solution ;)
It's basically a flag to say all allocations from this thread should
not recurse back into filesystem code. I'll either need to change
the allocations manually or keep this flag and write a comment
documenting why. I'll decide what to on my long airplane ride tomorrow
and will make sure it goes off to Linus' tree ASAP after that.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-10-15 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 6:59 deadlocks with fallocate Thomas Neumann
2009-10-14 15:09 ` Christoph Hellwig
2009-10-14 23:16 ` Thomas Neumann
2009-10-15 5:58 ` Thomas Neumann
2009-10-15 12:13 ` Christoph Hellwig [this message]
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=20091015121345.GA18234@infradead.org \
--to=hch@infradead.org \
--cc=linux-xfs@oss.sgi.com \
--cc=tneumann@users.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox