From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF662ECAAD5 for ; Fri, 9 Sep 2022 03:01:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229529AbiIIDBO (ORCPT ); Thu, 8 Sep 2022 23:01:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35752 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229577AbiIIDBI (ORCPT ); Thu, 8 Sep 2022 23:01:08 -0400 Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0D756114A65 for ; Thu, 8 Sep 2022 20:01:07 -0700 (PDT) Received: by mail-pj1-x1033.google.com with SMTP id q15-20020a17090a304f00b002002ac83485so291113pjl.0 for ; Thu, 08 Sep 2022 20:01:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to:subject :user-agent:mime-version:date:message-id:from:to:cc:subject:date; bh=43jwGnS59LTzri1tkRF1HTsqNOy+AaUcwDQj3xSUi9Y=; b=qM7Qs8uwZ40xVP0T/DV9fdTIwI8Ar1eOIcgUKjE3i9KoFTMohzGLYbHkhwyqZe7E0d Q1YmX6zciTiD7MuhNmdVrE3y0P4WyTeQNRE/4WUPtdHtX1LOLatHiueeuNJBzYIqHTpA izuKDQlivt/6Fj0DEObTu6oJxDRZHjHxZZ8xP8xpJ1uwQwOzEv8vAI5YduienxUtn/xc grqIzRFQMPivQAgRzcDBA5D5Cxh/ZUJJEXrkD/TbmOzd3d5owHGQyD1twfxhyyKqvrit uFpsDm70Mcz7N4AZJ6rjz1dFaGIsnntIj0ZXETPId6ungfNrNRz5p7IpTS7QqyD4AR2f GkFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to:subject :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date; bh=43jwGnS59LTzri1tkRF1HTsqNOy+AaUcwDQj3xSUi9Y=; b=R0920xw1iWUagwqCDR5K/lINiM838IF/Zy5/wEIz4mGUBCNpb9513t0fKfaI+AvBA7 jaWTmbzt6BIFMSuV3XyDc2OKyLATE2XfJtTv/jvuL3tQZLLzkVVG8O/Y72IIiFl+53FI AOZCtkQbpDNBCt+s6Fwmc6rYQaV1WAAsK7Y/q61/2wgfPNFyOEnzIlsxTr0gzrnpy/RQ nvQXecHTBPRwYRHq7E0PCg6REf7mEooGXA1GdehuwkIYvDsJasxt49U/nhJYwjnLCnMQ 6zw8zye5R8CkeRGJDOORnfacJthxLYgfd+s86kQzltmhuRhMW5cwERQvu1Nwrr83eFjW Aztg== X-Gm-Message-State: ACgBeo1CW8FKYhJBjX1hLRgila9fnOQNWXcirJ/gO6xrQnNRJm+NMYVJ iCu0rm59PWSAMecUnZhhXzZyFA== X-Google-Smtp-Source: AA6agR6BsP2ZvqecHewGiBFc53IL03+Xq/d1KflcwXIs2xvLmXq+uxFUFgIrTgmPdTq6yhFSncXrWA== X-Received: by 2002:a17:902:ea02:b0:176:afd7:3d1d with SMTP id s2-20020a170902ea0200b00176afd73d1dmr11724510plg.120.1662692466553; Thu, 08 Sep 2022 20:01:06 -0700 (PDT) Received: from [10.4.159.81] ([139.177.225.228]) by smtp.gmail.com with ESMTPSA id c20-20020a656754000000b0042af14719f4sm198700pgu.51.2022.09.08.20.01.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 08 Sep 2022 20:01:06 -0700 (PDT) Message-ID: <262052c8-c03c-24c4-9163-5df8e9f312be@bytedance.com> Date: Fri, 9 Sep 2022 11:00:57 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: [Phishing Risk] Re: [Phishing Risk] Re: [Phishing Risk] [External] Re: [PATCH] cgroup/cpuset: Add a new isolated mems.policy type. To: Tejun Heo Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220902063303.1057-1-hezhongkun.hzk@bytedance.com> From: Zhongkun He In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tejun, > Hello, > > On Wed, Sep 07, 2022 at 08:06:30PM +0800, Zhongkun He wrote: >> It would be better if one process had a way to dynamically modify the >> mempolicy of another process. But unfortunately there is no interface or >> system call to do that in userspace. > > If you need to change the properties dynamically, I suggest adding this as a > dynamic per-process interface first. That's more generic and useful for more > cases. > > Thanks. Got it, thanks for your suggestion and reply.