From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Chengyu Song <csong84@gatech.edu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
taesoo@gatech.edu, changwoo@gatech.edu, sanidhya@gatech.edu,
blee@gatech.edu
Subject: Re: [PATCH 1/1] hfs: incorrect return values
Date: Wed, 25 Mar 2015 09:54:42 -0700 [thread overview]
Message-ID: <1427302482.2888.7.camel@slavad-ubuntu-14.04> (raw)
In-Reply-To: <1427243843-25929-1-git-send-email-csong84@gatech.edu>
On Tue, 2015-03-24 at 20:37 -0400, Chengyu Song wrote:
> In case of memory allocation error, the return should be -ENOMEM,
> instead of -ENOSPC.
>
To be honest, I am not fully sure that such fix makes sense. Of course,
it is possible to exchange -ENOSPC on -ENOMEM. But principally it is not
critical to use as -ENOSPC as -ENOMEM in such situation, from my point
of view.
Anyway, it is possible to change error code here.
Thanks,
Vyacheslav Dubeyko.
prev parent reply other threads:[~2015-03-25 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 0:37 [PATCH 1/1] hfs: incorrect return values Chengyu Song
2015-03-25 16:54 ` Viacheslav Dubeyko [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=1427302482.2888.7.camel@slavad-ubuntu-14.04 \
--to=slava@dubeyko.com \
--cc=blee@gatech.edu \
--cc=changwoo@gatech.edu \
--cc=csong84@gatech.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanidhya@gatech.edu \
--cc=taesoo@gatech.edu \
/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;
as well as URLs for NNTP newsgroup(s).