Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4145365yba; Wed, 17 Apr 2019 05:40:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqyM/49cOc96AyweVzO6sMHRXrCyv30mb3Gz45I5yvjWzUr1AVyh8NkdR4O/tFAeqiudJWxF X-Received: by 2002:a17:902:8a8b:: with SMTP id p11mr88579167plo.227.1555504818338; Wed, 17 Apr 2019 05:40:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555504818; cv=none; d=google.com; s=arc-20160816; b=o4aTeScOS460ySp0kwZ2WP1816Pli68XBWCFgFvCSx9BM97RM+ZFqph+Y375D8t4iP WEJe5/h8q9+1P758qngt8ooIkP/Rhf2vrSi+cmDansoVDmdV0o1etxoU+X7eNIo3v+l+ LByHe6tqkZxkmhURDl7xqsIPTQZfoB38rpJD+bAKEvHjwvc/wGuVKf65cKFlItIH2wiI xVcH8ORXKajPmqOIDWoqV4zHgGVKGuZ25gMytj23FJ0OL02HJBKIIFB7eCIhO3+YYaO5 fEFAswB4ZGIVyDz+MNEOWSeDekSJ8/SVMnvX3CO/o2ApS2rdhGXbb/t+w8tMqpKdNTeh gBmw== 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-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=rrlGYJVOHOmd+w94iAKkb9bPiDdoO923FRXZHboLrtQ=; b=iuc2qtpq7qe2Xn8LS5gkHqEf/RdPJDBCwjF30AWDeQJywiRi9VFiRrHBBQu1BJfgB7 osZBJlM/sLo6Z2QmwToI4wo09D+FsOQUSaQq5WGL523XcUw+hLYvbm5aI0zxeZzrMmZo QZOSjhYTcFGrQs0B9sG6vuXnJfPkhFNmEM7nVIOO0rSBoU0uR0rOnSs6G2m/swesVnXR HEUuznjjoHbDybiAib2Xs9yvJNfQ+S91gHVi6dDyBhWFIPhuLxPeg2SgZXf3Sz0i0SS4 UCFXYB5fmpCG8Py8t9XvXrw+UMA6QmjAKJ0wLTR5ABQRmY8tXvPc1mpzwl5TM1446XMW YEmQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="S6eJPv/C"; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s18si50036964plq.244.2019.04.17.05.40.03; Wed, 17 Apr 2019 05:40:18 -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; dkim=pass header.i=@gmail.com header.s=20161025 header.b="S6eJPv/C"; 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=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732183AbfDQMiq (ORCPT + 99 others); Wed, 17 Apr 2019 08:38:46 -0400 Received: from mail-lj1-f196.google.com ([209.85.208.196]:43724 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726800AbfDQMip (ORCPT ); Wed, 17 Apr 2019 08:38:45 -0400 Received: by mail-lj1-f196.google.com with SMTP id f18so22275160lja.10 for ; Wed, 17 Apr 2019 05:38:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=rrlGYJVOHOmd+w94iAKkb9bPiDdoO923FRXZHboLrtQ=; b=S6eJPv/CaIwbVKl8QkKfm0yv46I2+7FhSr+DoBBCsVCAgpCx+ZS4Wn6Bmu/8QTdpmQ 1UowURww6+i6MonLSLw4YkwsNL6AjkaX0/LyIY+G4KRIa8IParSvEd5Hxa0XVrgkovX1 noKeArPAGX1/TCDaukhhxJg/R1M/KcC9pA06Df/3mDVYmslfAyFVBWoRjjQlnbj/tvZx FrcfkTgoNf36Vh0edB4AaPLi2RyXHcL2SZOolE8I7E07GFgOp4pMH+xerLJQofp+i4oV z7MKNG1e7AjQDXhwG74JbqFm1LuC2OhKHvmj/vnp/3lm8Depud38iCrTseugEG9eoZAU n5uQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=rrlGYJVOHOmd+w94iAKkb9bPiDdoO923FRXZHboLrtQ=; b=BN/2rU4FbM0FHf5m6VTu08TC30aobiDaA6FB2I1U1ZnFZ9zln4O1aR3VvK1zYJobDh AUbJmlwnrWggl7a+DOKEX1wYICUziTfO2GVF76vLfBjeekYwNHBHcFpcODWWmByaavqv M7uOUXLP9La3Slr0MNKCG5BwUNFvuW3hR9LTNMxifHrkWY+Ubuhkab+CmRjQsmgKFllr aeSmGmu2IZV8EzThvzAxWARLJChDGXs0HbdTAUXNHTf1p2eKLvKonx90vbgNEQhpBOnz xl9dV0TKg5mUZhgVpv1Io1IoVadRG9AhQd6OVyk7gerV2IsTowDo6je7+WDgJvWFJrTE KOZQ== X-Gm-Message-State: APjAAAX4zHCvcxW9IdO+nOFbQUqCVGmp7jX7un6PnoNIu7wDTPrFtu+a YQoc7oiIXrACSZdEPCQdIas= X-Received: by 2002:a2e:8e96:: with SMTP id z22mr46915406ljk.123.1555504723735; Wed, 17 Apr 2019 05:38:43 -0700 (PDT) Received: from uranus.localdomain ([5.18.103.226]) by smtp.gmail.com with ESMTPSA id l15sm10869208ljh.62.2019.04.17.05.38.42 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 17 Apr 2019 05:38:42 -0700 (PDT) Received: by uranus.localdomain (Postfix, from userid 1000) id D62474600FF; Wed, 17 Apr 2019 15:38:41 +0300 (MSK) Date: Wed, 17 Apr 2019 15:38:41 +0300 From: Cyrill Gorcunov To: Michal =?iso-8859-1?Q?Koutn=FD?= Cc: Andrew Morton , Sergey Senozhatsky , kbuild-all@01.org, LKML , Michal Hocko , Randy Dunlap , Andrey Vagin , Andrew Morton , Pavel Emelyanov , Michael Kerrisk , Yang Shi , kbuild test robot Subject: Re: [PATCH] prctl: Don't compile some of prctl functions when CRUI Message-ID: <20190417123841.GA3040@uranus.lan> References: <20180420140044.478b4c88d3cf238bd440f2a7@linux-foundation.org> <20190417122349.GA15498@blackbody.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190417122349.GA15498@blackbody.suse.cz> User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 17, 2019 at 02:23:50PM +0200, Michal Koutn? wrote: > Hi. > > I see this discussion somewhat faded away since the previous year. > > There was rework [1] that reduced (ab)use of mmap_sem in prctl > functions. > > Actually, there still remains the down_write() in prctl_set_mm. > I considered at least replacing it with the mm_struct.arg_lock + > down_read() but then I learnt about this thread intending to remove that > part completely. I wouldn't oppose if CRIU is the sole (aware) user. > > Ad the bot build issue, I could build the kernel both with > CONFIG_CHECKPOINT_RESTORE and without CONFIG_CHECKPOINT_RESTORE just > fine after applying the two proposed patches. > > What is the current state? Perhaps, this change should be CCed to > linux-api@vger.kernel.org(?). > > [1] https://lore.kernel.org/lkml/1523730291-109696-1-git-send-email-yang.shi@linux.alibaba.com/T/ Hi! I've a bit vague memory what we've ended up with, but iirc there was a problem with brk() syscall or similar. Then I think we left everything as is. I think there is no much activity in this prctl area now as far as i know (replying to what is current state).