From: Mike Kravetz <mike.kravetz@oracle.com>
To: 'Andrew Morton' <akpm@linux-foundation.org>
Cc: Hillf Danton <hillf.zj@alibaba-inc.com>,
linux-mm@kvack.org, 'linux-kernel' <linux-kernel@vger.kernel.org>,
'Hugh Dickins' <hughd@google.com>,
'Dave Hansen' <dave.hansen@linux.intel.com>,
'Naoya Horiguchi' <n-horiguchi@ah.jp.nec.com>,
'Davidlohr Bueso' <dave@stgolabs.net>
Subject: Re: [PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes
Date: Mon, 2 Nov 2015 09:39:14 -0800 [thread overview]
Message-ID: <56379FC2.8000803@oracle.com> (raw)
In-Reply-To: <013501d11519$2e5e6940$8b1b3bc0$@alibaba-inc.com>
On 11/01/2015 06:50 PM, Hillf Danton wrote:
> Andrew, please correct me if I miss/mess anything.
>
>>> This hunk is already in the next tree, see below please.
>>>
>>
>> Ah, the whole series to add shmem like code to handle hole punch/fault
>> races is in the next tree. It has been determined that most of this
>> series is not necessary. For the next tree, ideally the following
>> should happen:
>> - revert the series
>> 0830d5afd4ab69d01cf5ceba9b9f2796564c4eb6
>> 4e0a78fea078af972276c2d3aeaceb2bac80e033
>> 251c8a023a0c639725e014a612e8c05a631ce839
>> 03bcef375766af4db12ec783241ac39f8bf5e2b1
>> - Add this patch (if Ack'ed/reviewed) to fix remove_inode_hugepages
>> - Add a new patch for the handle hole punch/fault race. It modifies
>> same code as this patch, so I have not sent out until this is Ack'ed.
>>
>> I will admit that I do not fully understand how maintainers manage their
>> trees and share patches. If someone can make suggestions on how to handle
>> this situation (create patches against what tree? send patches to who?),
>> I will be happy to make it happen.
>>
> The rule is to prepare patches against the next tree and deliver patches to
> linux-mm with AKPM, linux-kernel cced. The authors and maintainers of the
> current code your patches change should also be cced.
> And those guys you want to get ack and comments.
>
> In this case, you should first ask Andrew to withdraw the 4 commits.
> Then send your new patches, one after another, one problem a patch.
>
> Best Wishes
> Hillf
Andrew,
As mentioned above, it has been determined that most of the series titled
"[PATCH v2 0/4] hugetlbfs fallocate hole punch race with page faults" is
unnecessary. Ideally, we want to remove this entire series from mmotm and
linux-next. It will be replaced with a simpler patch.
However, before that happens I would like to address bugs in the current
code as pointed out by Hugh Dickins. These are addresses in the patch
which started this thread:
"[PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes"
If there is a way to do this that makes your work easier let me know.
It would be good if someone could take a look at this patch as these bugs
also exist in 4.3.
--
Mike Kravetz
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Mike Kravetz <mike.kravetz@oracle.com>
To: "'Andrew Morton'" <akpm@linux-foundation.org>
Cc: Hillf Danton <hillf.zj@alibaba-inc.com>,
linux-mm@kvack.org,
"'linux-kernel'" <linux-kernel@vger.kernel.org>,
"'Hugh Dickins'" <hughd@google.com>,
"'Dave Hansen'" <dave.hansen@linux.intel.com>,
"'Naoya Horiguchi'" <n-horiguchi@ah.jp.nec.com>,
"'Davidlohr Bueso'" <dave@stgolabs.net>
Subject: Re: [PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes
Date: Mon, 2 Nov 2015 09:39:14 -0800 [thread overview]
Message-ID: <56379FC2.8000803@oracle.com> (raw)
In-Reply-To: <013501d11519$2e5e6940$8b1b3bc0$@alibaba-inc.com>
On 11/01/2015 06:50 PM, Hillf Danton wrote:
> Andrew, please correct me if I miss/mess anything.
>
>>> This hunk is already in the next tree, see below please.
>>>
>>
>> Ah, the whole series to add shmem like code to handle hole punch/fault
>> races is in the next tree. It has been determined that most of this
>> series is not necessary. For the next tree, ideally the following
>> should happen:
>> - revert the series
>> 0830d5afd4ab69d01cf5ceba9b9f2796564c4eb6
>> 4e0a78fea078af972276c2d3aeaceb2bac80e033
>> 251c8a023a0c639725e014a612e8c05a631ce839
>> 03bcef375766af4db12ec783241ac39f8bf5e2b1
>> - Add this patch (if Ack'ed/reviewed) to fix remove_inode_hugepages
>> - Add a new patch for the handle hole punch/fault race. It modifies
>> same code as this patch, so I have not sent out until this is Ack'ed.
>>
>> I will admit that I do not fully understand how maintainers manage their
>> trees and share patches. If someone can make suggestions on how to handle
>> this situation (create patches against what tree? send patches to who?),
>> I will be happy to make it happen.
>>
> The rule is to prepare patches against the next tree and deliver patches to
> linux-mm with AKPM, linux-kernel cced. The authors and maintainers of the
> current code your patches change should also be cced.
> And those guys you want to get ack and comments.
>
> In this case, you should first ask Andrew to withdraw the 4 commits.
> Then send your new patches, one after another, one problem a patch.
>
> Best Wishes
> Hillf
Andrew,
As mentioned above, it has been determined that most of the series titled
"[PATCH v2 0/4] hugetlbfs fallocate hole punch race with page faults" is
unnecessary. Ideally, we want to remove this entire series from mmotm and
linux-next. It will be replaced with a simpler patch.
However, before that happens I would like to address bugs in the current
code as pointed out by Hugh Dickins. These are addresses in the patch
which started this thread:
"[PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes"
If there is a way to do this that makes your work easier let me know.
It would be good if someone could take a look at this patch as these bugs
also exist in 4.3.
--
Mike Kravetz
next prev parent reply other threads:[~2015-11-02 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 5:07 [PATCH] mm/hugetlbfs Fix bugs in fallocate hole punch of areas with holes Hillf Danton
2015-10-31 5:07 ` Hillf Danton
2015-10-31 17:53 ` Mike Kravetz
2015-10-31 17:53 ` Mike Kravetz
2015-11-02 2:50 ` Hillf Danton
2015-11-02 2:50 ` Hillf Danton
2015-11-02 17:39 ` Mike Kravetz [this message]
2015-11-02 17:39 ` Mike Kravetz
2015-11-02 21:40 ` Andrew Morton
2015-11-02 21:40 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2015-10-30 23:32 Mike Kravetz
2015-10-30 23:32 ` Mike Kravetz
2015-11-09 6:57 ` Naoya Horiguchi
2015-11-09 6:57 ` Naoya Horiguchi
2015-11-09 7:09 ` Hugh Dickins
2015-11-09 7:09 ` Hugh Dickins
2015-11-09 23:24 ` Mike Kravetz
2015-11-09 23:24 ` Mike Kravetz
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=56379FC2.8000803@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=hillf.zj@alibaba-inc.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.