Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp372415imm; Wed, 13 Jun 2018 01:37:56 -0700 (PDT) X-Google-Smtp-Source: ADUXVKLVtJdJ78GSeRjgInN2BWfBHsPWgkG/qEcbDJ+kB+pwvu0BZo/LLZUPgCJHp/G34OZe6FFf X-Received: by 2002:a62:d9c5:: with SMTP id b66-v6mr3955297pfl.41.1528879076364; Wed, 13 Jun 2018 01:37:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528879076; cv=none; d=google.com; s=arc-20160816; b=gaKs1uiEnQ3dfTOe1IQWhcCgrf82ioKFk3TSfPiikZM+ruXoY2+S0Fbz7YyixjYohU iEZas5dwE3luFWUJmoO9uZoe3FFR22I0uksvrkIKnjw5SfObvl5AyRwBow/uTrm/qKS0 MlX1njhuJJ4ea4aKom2atY1QEm9ptr7ttQUwFhLSJdVd5PmZZAVZCk5r9aXuJ9GJGcut 9taDy642DjAUamfKuwtc6VYrHd1ovQlHblfJZkWT05SgyKTdIXXHpeRPvR9awDvDK9W7 x6K9v23kNIC8gtiEiYITd0Tdb1U3REaHai8T/LUobTVwQYtgrnr8vND5t83J5avyjTK4 +EKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=ZOsU+hy0g967+SOw1PwcrTRl+XDua85/7pIMRum+FEg=; b=GR5MVs4GgLwOPRrFUnl2SBBk/GxnnyS5TilcIXWMQPPgKrIHfC1n0XD76Hd431Fo1e 9bHMdjShinrok+KXiLIKfKCXZJT9G/BX6C+D+gl96fIFT8dZESQWhZWkxbT77AzHRhfe nf9d4tQoLdVbhR9JyEDzvnQtPVmW4Go2R01ktKwB97AsuiJnaYd7f4XNtOOvj8EaM8Me S2+jbtEnn+saNnmbbAOyWxlOLKNL2EqUdP4onwanKnLbMrg7h4hQTTWltEsBTMHZY1CC 8jhqpADMprOBVxf0n8ljjTNdvBHORZgeH6T8LNko/MRmm0ZzTrTQ0z0m9Leo8rZrPjCl qAQg== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p21-v6si1862268pgv.112.2018.06.13.01.37.41; Wed, 13 Jun 2018 01:37:56 -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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934679AbeFMIhN (ORCPT + 99 others); Wed, 13 Jun 2018 04:37:13 -0400 Received: from mx2.suse.de ([195.135.220.15]:45984 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933912AbeFMIhK (ORCPT ); Wed, 13 Jun 2018 04:37:10 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 08B4CAD88; Wed, 13 Jun 2018 08:37:09 +0000 (UTC) Date: Wed, 13 Jun 2018 10:37:07 +0200 From: Michal Hocko To: Vlastimil Babka Cc: Jason Baron , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Joonsoo Kim , Mel Gorman , "Kirill A. Shutemov" , linux-api@vger.kernel.org, emunson@mgebm.net Subject: Re: [PATCH] mm/madvise: allow MADV_DONTNEED to free memory that is MLOCK_ONFAULT Message-ID: <20180613083707.GE13364@dhcp22.suse.cz> References: <1528484212-7199-1-git-send-email-jbaron@akamai.com> <20180611072005.GC13364@dhcp22.suse.cz> <4c4de46d-c55a-99a8-469f-e1e634fb8525@akamai.com> <20180611150330.GQ13364@dhcp22.suse.cz> <775adf2d-140c-1460-857f-2de7b24bafe7@akamai.com> <20180612074646.GS13364@dhcp22.suse.cz> <5a9398f4-453c-5cb5-6bbc-f20c3affc96a@akamai.com> <0daccb7c-f642-c5ce-ca7a-3b3e69025a1e@suse.cz> <20180613071552.GD13364@dhcp22.suse.cz> <5eb9a018-d5ac-5732-04f1-222c343b840a@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5eb9a018-d5ac-5732-04f1-222c343b840a@suse.cz> User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 13-06-18 09:51:23, Vlastimil Babka wrote: > On 06/13/2018 09:15 AM, Michal Hocko wrote: > > On Wed 13-06-18 08:32:19, Vlastimil Babka wrote: [...] > >> I think more concerning than guaranteeing no later major fault is > >> possible data loss, e.g. replacing data with zero-filled pages. > > > > But MADV_DONTNEED is an explicit call for data loss. Or do I miss your > > point? > > My point is that if somebody is relying on MADV_DONTNEED not affecting > mlocked pages, the consequences will be unexpected data loss, not just > extra page faults. OK, I see your point now. I would consider this an application bug though. Calling MADV_DONTNEED and wondering that the content is gone is, ehm, questionable at best. Why would anybody do that in the first place? Anyway, I think that we cannot change the behavior because of mlockall semantic as mentioned earlier. -- Michal Hocko SUSE Labs