lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170113102742.686b785c@lwn.net>
Date:   Fri, 13 Jan 2017 10:27:42 -0700
From:   Jonathan Corbet <corbet@....net>
To:     "W. Trevor King" <wking@...mily.us>
Cc:     Li Zefan <lizefan@...wei.com>, cgroups@...r.kernel.org,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Documentation: cpuset: Fix 'cpuset.tasks' -> 'tasks'

On Thu, 12 Jan 2017 14:24:27 -0800
"W. Trevor King" <wking@...mily.us> wrote:

> This looks like it was accidentally caught up in e21a05cb (doc:
> cpuset: Update the cpuset flag file, 2010-02-24).
> 
> While I'm touching the line, also fix the posessive "cpusets" ->
> "cpuset's".
> 
> Signed-off-by: W. Trevor King <wking@...mily.us>
> ---
>  Documentation/cgroup-v1/cpusets.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> This patch is based on v4.9, but the lines I'm touching don't churn
> much so it should apply to any recent version.
> 
> diff --git a/Documentation/cgroup-v1/cpusets.txt b/Documentation/cgroup-v1/cpusets.txt
> index e5ac5da86..8402dd6 100644
> --- a/Documentation/cgroup-v1/cpusets.txt
> +++ b/Documentation/cgroup-v1/cpusets.txt
> @@ -615,7 +615,7 @@ to allocate a page of memory for that task.
>  
>  If a cpuset has its 'cpuset.cpus' modified, then each task in that cpuset
>  will have its allowed CPU placement changed immediately.  Similarly,
> -if a task's pid is written to another cpusets 'cpuset.tasks' file, then its
> +if a task's pid is written to another cpuset's 'tasks' file, then its

So I'll confess that I don't understand this change.  All of the control
files are referred to as cpuset.whatever in this document; why should
this one, in particular, be different?

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ