From: Mike Kravetz <mike.kravetz@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: yuyufen <yuyufen@huawei.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] hugetlbfs: always use address space in inode for resv_map pointer
Date: Thu, 9 May 2019 16:32:02 -0700 [thread overview]
Message-ID: <31754605-5425-a2aa-b16f-ad89772c27b9@oracle.com> (raw)
In-Reply-To: <20190509161135.00b542e5b4d0996b5089ea02@linux-foundation.org>
On 5/9/19 4:11 PM, Andrew Morton wrote:
> On Wed, 8 May 2019 13:16:09 -0700 Mike Kravetz <mike.kravetz@oracle.com> wrote:
>
>>> I think it is better to add fixes label, like:
>>> Fixes: 58b6e5e8f1ad ("hugetlbfs: fix memory leak for resv_map")
>>>
>>> Since the commit 58b6e5e8f1a has been merged to stable, this patch also be needed.
>>> https://www.spinics.net/lists/stable/msg298740.html
>>
>> It must have been the AI that decided 58b6e5e8f1a needed to go to stable.
>
> grr.
>
>> Even though this technically does not fix 58b6e5e8f1a, I'm OK with adding
>> the Fixes: to force this to go to the same stable trees.
>
> Why are we bothering with any of this, given that
>
> : Luckily, private_data is NULL for address spaces in all such cases
> : today but, there is no guarantee this will continue.
>
> ?
You are right. For stable releases, I do not see any way for this to
be an issue. We are lucky today (and in the past). The patch is there
to guard against code changes which may cause this condition to change
in the future.
Yufen Yu, do you see this actually fixing a problem in stable releases?
I believe you originally said this is not a problem today, which would
also imply older releases. Just want to make sure I am not missing something.
--
Mike Kravetz
> Even though 58b6e5e8f1ad was inappropriately backported, the above
> still holds, so what problem does a backport of "hugetlbfs: always use
> address space in inode for resv_map pointer" actually solve?
>
> And yes, some review of this would be nice
next prev parent reply other threads:[~2019-05-09 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 4:02 [PATCH] hugetlbfs: move resv_map to hugetlbfs_inode_info Yufen Yu
2019-04-12 23:40 ` Mike Kravetz
2019-04-13 11:57 ` yuyufen
2019-04-15 6:16 ` Naoya Horiguchi
2019-04-15 9:15 ` Michal Hocko
2019-04-15 17:11 ` Mike Kravetz
2019-04-15 23:59 ` Naoya Horiguchi
2019-04-16 0:37 ` Mike Kravetz
2019-04-16 6:50 ` Michal Hocko
2019-04-19 20:44 ` [PATCH] hugetlbfs: always use address space in inode for resv_map pointer Mike Kravetz
2019-05-08 7:10 ` yuyufen
2019-05-08 20:16 ` Mike Kravetz
2019-05-09 23:11 ` Andrew Morton
2019-05-09 23:32 ` Mike Kravetz [this message]
2019-04-16 12:57 ` [PATCH] hugetlbfs: move resv_map to hugetlbfs_inode_info 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=31754605-5425-a2aa-b16f-ad89772c27b9@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=stable@vger.kernel.org \
--cc=yuyufen@huawei.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