From: yuyufen <yuyufen@huawei.com>
To: Mike Kravetz <mike.kravetz@oracle.com>, <linux-mm@kvack.org>
Cc: <kirill.shutemov@linux.intel.com>, <n-horiguchi@ah.jp.nec.com>,
<mhocko@kernel.org>, <yuyufen@huawei.com>
Subject: Re: [PATCH] hugetlbfs: fix protential null pointer dereference
Date: Wed, 10 Apr 2019 12:20:50 +0800 [thread overview]
Message-ID: <1a43c780-3ded-a7bc-391e-f85295eb942d@huawei.com> (raw)
In-Reply-To: <e8dd99bb-c357-962a-9f29-b7f25c636714@oracle.com>
Hi, Mike
On 2019/4/10 11:38, Mike Kravetz wrote:
> On 4/9/19 7:50 PM, Yufen Yu wrote:
>> After commit 58b6e5e8f1ad ("hugetlbfs: fix memory leak for resv_map"),
>> i_mapping->private_data will be NULL for mode that is not regular and link.
>> Then, it might cause NULL pointer derefernce in hugetlb_reserve_pages()
>> when do_mmap. We can avoid protential null pointer dereference by
>> judging whether it have been allocated.
>>
>> Fixes: 58b6e5e8f1ad ("hugetlbfs: fix memory leak for resv_map")
>> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
>> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>> Cc: Michal Hocko <mhocko@kernel.org>
>> Signed-off-by: Yufen Yu <yuyufen@huawei.com>
> Thanks for catching this. I mistakenly thought all the code was checking
> for NULL resv_map. That certainly is one (and only) place where it is not
> checked. Have you verified that this is possible? Should be pretty easy
> to do. If you have not, I can try to verify tomorrow.
I honestly say that I don't have verified.
>> ---
>> mm/hugetlb.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
>> index 97b1e0290c66..15e4baf2aa7d 100644
>> --- a/mm/hugetlb.c
>> +++ b/mm/hugetlb.c
>> @@ -4465,6 +4465,8 @@ int hugetlb_reserve_pages(struct inode *inode,
>> */
>> if (!vma || vma->vm_flags & VM_MAYSHARE) {
>> resv_map = inode_resv_map(inode);
>> + if (!resv_map)
>> + return -EOPNOTSUPP;
> I'm not sure about the return code here. Note that all callers of
> hugetlb_reserve_pages() force return value of -ENOMEM if non-zero value
> is returned. I think we would like to return -EACCES in this situation.
> The mmap man page says:
>
> EACCES A file descriptor refers to a non-regular file. Or ...
Thanks for your suggestion. It is more reasonable to use -EACCES.
Yufen
Thanks.
next prev parent reply other threads:[~2019-04-10 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 2:50 Yufen Yu
2019-04-10 3:38 ` Mike Kravetz
2019-04-10 4:20 ` yuyufen [this message]
2019-04-10 18:56 ` Mike Kravetz
2019-04-11 3:30 ` yuyufen
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=1a43c780-3ded-a7bc-391e-f85295eb942d@huawei.com \
--to=yuyufen@huawei.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.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