From: "Paul Menage" <menage@google.com>
To: "Li Zefan" <lizf@cn.fujitsu.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] cgroup: switch to proc_create()
Date: Mon, 10 Mar 2008 14:01:33 -0700 [thread overview]
Message-ID: <6599ad830803101401s3b12bc85l53ef67f083ad761c@mail.gmail.com> (raw)
In-Reply-To: <47D4E3AC.2020600@cn.fujitsu.com>
On Mon, Mar 10, 2008 at 12:30 AM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> There is a race between create_proc_entry() and the assignment
> of file ops. proc_create() is invented to fix it.
>
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Acked-by: Paul Menage <menage@google.com>
Doesn't seem to be a serious race since there's nothing in userspace
at this point to read the file. But replacing four lines with one is
generally a good thing.
Paul
> ---
> kernel/cgroup.c | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index 8d833b6..8d45126 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -2489,7 +2489,6 @@ int __init cgroup_init(void)
> {
> int err;
> int i;
> - struct proc_dir_entry *entry;
>
> err = bdi_init(&cgroup_backing_dev_info);
> if (err)
> @@ -2505,9 +2504,7 @@ int __init cgroup_init(void)
> if (err < 0)
> goto out;
>
> - entry = create_proc_entry("cgroups", 0, NULL);
> - if (entry)
> - entry->proc_fops = &proc_cgroupstats_operations;
> + proc_create("cgroups", 0, NULL, &proc_cgroupstats_operations);
>
> out:
> if (err)
> --
> 1.5.4.rc3
>
next prev parent reply other threads:[~2008-03-10 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 7:30 Li Zefan
2008-03-10 21:01 ` Paul Menage [this message]
2008-03-10 23:43 ` Li Zefan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6599ad830803101401s3b12bc85l53ef67f083ad761c@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®