From: Christoph Hellwig <hch@infradead.org>
To: Felix Blyakher <felixb@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] xfs: fix getbmap vs mmap deadlock
Date: Thu, 9 Apr 2009 13:14:12 -0400 [thread overview]
Message-ID: <20090409171412.GB25303@infradead.org> (raw)
In-Reply-To: <2B47193B-9486-4500-80C4-E96750BEA54B@sgi.com>
On Mon, Apr 06, 2009 at 07:42:57PM -0500, Felix Blyakher wrote:
> Actually with the patch we either get all requested extents, or none
> if we fail to get memory for them.
> Should we teach the callers to expect ENOMEM and repeat the call
> to xfs_getbmap with smaller number of extents?
The problem with any of that is that we don't actually get the exact
extent list but always a racy version.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-09 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 13:39 [PATCH 2/2] xfs: fix getbmap vs mmap deadlock Christoph Hellwig
2009-03-16 6:30 ` Christoph Hellwig
2009-03-29 7:44 ` Christoph Hellwig
2009-04-06 23:56 ` Eric Sandeen
2009-04-07 0:42 ` Felix Blyakher
2009-04-09 17:14 ` Christoph Hellwig [this message]
2009-04-16 16:05 ` Felix Blyakher
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=20090409171412.GB25303@infradead.org \
--to=hch@infradead.org \
--cc=felixb@sgi.com \
--cc=xfs@oss.sgi.com \
/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