Received: by 10.213.65.68 with SMTP id h4csp1062166imn; Wed, 21 Mar 2018 01:23:59 -0700 (PDT) X-Google-Smtp-Source: AG47ELuesyPnCzBldLETWfxB3dLF9jTfz2LHzMOIILz/JVcsupf7N336aC47J7ROh+cs5g1rjf4o X-Received: by 10.101.97.21 with SMTP id z21mr33246pgu.163.1521620639432; Wed, 21 Mar 2018 01:23:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521620639; cv=none; d=google.com; s=arc-20160816; b=pNvaVPy9r/EN1phdmjce24Mcod818VW2Fnn8GHSCd4KDIFPJSWF0742o4vJWagH35p unprcsZ7Co0KwZnz7eLn3K5q5mfooqRbR7Dvfee4C6xiT4sTUyagrBd17K4R883szNqw U8rZjv20BE/39k1s5N00Vr1jSQtbWnPJY1baOk7KedsaUgz6a8GXr8AmGwQ9usWnrd+N JcgdZ3Cs7xzYHkpEX/a4wEY+voAaxvhW7FuNR5i80mTsslTCfjTUHdjzh6Z13oYQqH3p A+dazG7TL/NY9+3EIcf3iFUGm8i7iJe4eDSfuQmfhM2eBFSDPUEXbyGZeN88fcJB50pa kf9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:to:subject:arc-authentication-results; bh=FtuT+01DLnaCVoCRvwxqInRDXyap5xMyaOQdF7Ds+PY=; b=0UAnJKCuZ/ml3MDvKi71RvdLeMBDqz+8khHVUvBq7UpuMMlOtMJtYvl/h/cOkyXCF/ BtuIQnE7sOnPkgxYG/54a9WLdkHnPfZ4nFGLNjyULmWfyIk1+buBZ/+zJt10GmfWntvZ osjDcz/oY8A9jPojEL13JEVYw5l+j2Wa+Bs6DFUriwsJQjO5Az5s878kHhQe93CNov23 qhWhdJFidIs2FKMz0+wkZhOmfLE8ytatcXMeUXxBQMPOxJLKCX1dLKWzgv9vUEn7a4LV cN5WbZ3eQfjzXduuyyBF23Y7aAcUgagZp+LW8zEPLL7diADMI2/Xx+Nk2ACd04iAAWIW HNzA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t11-v6si3274778plr.411.2018.03.21.01.23.45; Wed, 21 Mar 2018 01:23:59 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751923AbeCUIUc (ORCPT + 99 others); Wed, 21 Mar 2018 04:20:32 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:41802 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751902AbeCUIU2 (ORCPT ); Wed, 21 Mar 2018 04:20:28 -0400 Received: from pps.filterd (m0098414.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w2L8J8AZ056473 for ; Wed, 21 Mar 2018 04:20:27 -0400 Received: from e06smtp13.uk.ibm.com (e06smtp13.uk.ibm.com [195.75.94.109]) by mx0b-001b2d01.pphosted.com with ESMTP id 2guk4rhkm4-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Wed, 21 Mar 2018 04:20:27 -0400 Received: from localhost by e06smtp13.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 21 Mar 2018 08:20:26 -0000 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) by e06smtp13.uk.ibm.com (192.168.101.143) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 21 Mar 2018 08:20:22 -0000 Received: from d06av24.portsmouth.uk.ibm.com (mk.ibm.com [9.149.105.60]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w2L8KMwS50987058; Wed, 21 Mar 2018 08:20:22 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9CD2E42047; Wed, 21 Mar 2018 08:12:29 +0000 (GMT) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 0BB0942041; Wed, 21 Mar 2018 08:12:29 +0000 (GMT) Received: from [9.145.172.250] (unknown [9.145.172.250]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 21 Mar 2018 08:12:28 +0000 (GMT) Subject: Re: [PATCH] mm/hugetlb: prevent hugetlb VMA to be misaligned To: Mike Kravetz , akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrea Arcangeli , mhocko@kernel.org, Dan Williams References: <1521566754-30390-1-git-send-email-ldufour@linux.vnet.ibm.com> <86240c1a-d1f1-0f03-855e-c5196762ec0a@oracle.com> <0d24f817-303a-7b4d-4603-b2d14e4b391a@oracle.com> From: Laurent Dufour Date: Wed, 21 Mar 2018 09:20:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <0d24f817-303a-7b4d-4603-b2d14e4b391a@oracle.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18032108-0012-0000-0000-000005C1A1D6 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18032108-0013-0000-0000-0000193DC31F Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-03-21_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1803210102 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/03/2018 22:35, 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 > 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. FWIW, Reviewed-by: Laurent Dufour Tested-by: Laurent Dufour > Fixes: 31383c6865a5 ("mm, hugetlbfs: introduce ->split() to vm_operations_struct) > Reported by: Laurent Dufour > Signed-off-by: Mike Kravetz > --- > 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, >