From: David Rientjes <rientjes@google.com>
To: Wanpeng Li <liwp.linux@gmail.com>
Cc: Gavin Shan <shangw@linux.vnet.ibm.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
William Irwin <wli@holomorphy.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb: fix error code in hugetlbfs_alloc_inode
Date: Mon, 9 Jul 2012 19:01:04 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1207091859280.25143@chino.kir.corp.google.com> (raw)
In-Reply-To: <20120710011516.GA2457@kernel>
On Tue, 10 Jul 2012, Wanpeng Li wrote:
> >>diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
> >>index c4b85d0..79a0f33 100644
> >>--- a/fs/hugetlbfs/inode.c
> >>+++ b/fs/hugetlbfs/inode.c
> >>@@ -696,7 +696,7 @@ static struct inode *hugetlbfs_alloc_inode(struct super_block *sb)
> >> p = kmem_cache_alloc(hugetlbfs_inode_cachep, GFP_KERNEL);
> >> if (unlikely(!p)) {
> >> hugetlbfs_inc_free_inodes(sbinfo);
> >>- return NULL;
> >>+ return -ENOMEM;
> >
> >The function is expecting "struct inode *", man.
> >
> >static struct inode *hugetlbfs_alloc_inode(struct super_block *sb)
> >
> Hmm, replace it by ERR_PTR(-ENOMEM).
>
Please listen to the feedback you're getting before you reply.
This function is called by alloc_inode(). It tests whether the return
value is NULL or not, it doesn't check for PTR_ERR(). It's correct the
way it's written and you would have broken it.
In the future, please demonstrate how you've tested your patches before
proposing them.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-07-10 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 1:03 Wanpeng Li
2012-07-10 1:09 ` Gavin Shan
2012-07-10 1:15 ` Wanpeng Li
2012-07-10 2:01 ` David Rientjes [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=alpine.DEB.2.00.1207091859280.25143@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwp.linux@gmail.com \
--cc=shangw@linux.vnet.ibm.com \
--cc=wli@holomorphy.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