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 1/2] xfs: a couple getbmap cleanups
Date: Thu, 9 Apr 2009 13:11:35 -0400 [thread overview]
Message-ID: <20090409171135.GA25303@infradead.org> (raw)
In-Reply-To: <9EF64CF3-FDFC-4777-94A5-7295E827ABA4@sgi.com>
On Mon, Apr 06, 2009 at 07:57:48PM -0500, Felix Blyakher wrote:
> Shouldn't we set error to ENOMEM here?
Yes, good catch.
> Should the callers be taught to handle ENOMEM now?
The kernel callchain handles it, and in userspace the only caller
(xfs_io) will handled it by printing an out of memory message.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-09 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 13:38 [PATCH 1/2] xfs: a couple getbmap cleanups Christoph Hellwig
2009-03-16 6:30 ` Christoph Hellwig
2009-03-29 7:44 ` Christoph Hellwig
2009-04-06 23:10 ` Eric Sandeen
2009-04-07 0:57 ` Felix Blyakher
2009-04-09 17:11 ` Christoph Hellwig [this message]
2009-04-29 14:40 ` Felix Blyakher
2009-04-29 14:50 ` Christoph Hellwig
2009-04-29 15:02 ` Felix Blyakher
2009-04-29 15:04 ` Christoph Hellwig
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=20090409171135.GA25303@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