From: Michal Hocko <mhocko@kernel.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Laurent Dufour <ldufour@linux.vnet.ibm.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] mm/hugetlb: prevent hugetlb VMA to be misaligned
Date: Wed, 21 Mar 2018 09:41:13 +0100 [thread overview]
Message-ID: <20180321084113.GD23100@dhcp22.suse.cz> (raw)
In-Reply-To: <0d24f817-303a-7b4d-4603-b2d14e4b391a@oracle.com>
On Tue 20-03-18 14:35:28, Mike Kravetz wrote:
> On 03/20/2018 02:26 PM, Mike Kravetz wrote:
> > Thanks Laurent!
> >
> > This bug was introduced by 31383c6865a5. Dan's changes for 31383c6865a5
> > seem pretty straight forward. It simply replaces an explicit check when
> > splitting a vma to a new vm_ops split callout. Unfortunately, mappings
> > created via shmget/shmat have their vm_ops replaced. Therefore, this
> > split callout is never made.
> >
> > The shm vm_ops do indirectly call the original vm_ops routines as needed.
> > Therefore, I would suggest a patch something like the following instead.
> > If we move forward with the patch, we should include Laurent's BUG output
> > and perhaps test program in the commit message.
>
> Sorry, patch in previous mail was a mess
>
> >From 7a19414319c7937fd2757c27f936258f16c1f61d Mon Sep 17 00:00:00 2001
> From: Mike Kravetz <mike.kravetz@oracle.com>
> Date: Tue, 20 Mar 2018 13:56:57 -0700
> Subject: [PATCH] shm: add split function to shm_vm_ops
>
> The split function was added to vm_operations_struct to determine
> if a mapping can be split. This was mostly for device-dax and
> hugetlbfs mappings which have specific alignment constraints.
>
> mappings initiated via shmget/shmat have their original vm_ops
> overwritten with shm_vm_ops. shm_vm_ops functions will call back
> to the original vm_ops if needed. Add such a split function.
>
> Fixes: 31383c6865a5 ("mm, hugetlbfs: introduce ->split() to vm_operations_struct)
> Reported by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
Yes this looks much better than the original hugetlb specific code in
the generic vma code.
Please add the original VM_BUG_ON report to the changelog
Cc: stable
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> ipc/shm.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/ipc/shm.c b/ipc/shm.c
> index 7acda23430aa..50e88fc060b1 100644
> --- a/ipc/shm.c
> +++ b/ipc/shm.c
> @@ -386,6 +386,17 @@ static int shm_fault(struct vm_fault *vmf)
> return sfd->vm_ops->fault(vmf);
> }
>
> +static int shm_split(struct vm_area_struct *vma, unsigned long addr)
> +{
> + struct file *file = vma->vm_file;
> + struct shm_file_data *sfd = shm_file_data(file);
> +
> + if (sfd->vm_ops && sfd->vm_ops->split)
> + return sfd->vm_ops->split(vma, addr);
> +
> + return 0;
> +}
> +
> #ifdef CONFIG_NUMA
> static int shm_set_policy(struct vm_area_struct *vma, struct mempolicy *new)
> {
> @@ -510,6 +521,7 @@ static const struct vm_operations_struct shm_vm_ops = {
> .open = shm_open, /* callback for a new vm-area open */
> .close = shm_close, /* callback for when the vm-area is released */
> .fault = shm_fault,
> + .split = shm_split,
> #if defined(CONFIG_NUMA)
> .set_policy = shm_set_policy,
> .get_policy = shm_get_policy,
> --
> 2.13.6
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-03-21 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 17:25 Laurent Dufour
2018-03-20 21:26 ` Mike Kravetz
2018-03-20 21:35 ` Mike Kravetz
2018-03-21 8:20 ` Laurent Dufour
2018-03-21 8:41 ` Michal Hocko [this message]
2018-03-21 16:13 ` [PATCH v2] shm: add split function to shm_vm_ops Mike Kravetz
2018-03-21 18:42 ` Dan Williams
2018-03-21 20:56 ` Andrew Morton
2018-03-21 22:53 ` Mike Kravetz
2018-03-21 8:18 ` [PATCH] mm/hugetlb: prevent hugetlb VMA to be misaligned Laurent Dufour
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=20180321084113.GD23100@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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
all inboxes | Powered by JetHome®