From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-ext4@vger.kernel.org
Cc: Alex Tomas <alex@clusterfs.com>, Mike Travis <travis@sgi.com>
Subject: Unusual code in mballoc.c.
Date: Sun, 28 Sep 2008 11:56:12 +1000 [thread overview]
Message-ID: <200809281156.12688.rusty@rustcorp.com.au> (raw)
Hi all,
A grep lead me to fs/ext4/mballoc.c:
Line 2551:
for (i = 0; i < nr_cpu_ids; i++) {
This is more normally "for_each_possible_cpu(i)".
Line 4097:
ac->ac_lg = &sbi->s_locality_groups[get_cpu()];
put_cpu();
This is presumably someone suppressing a warning. It should be:
ac->ac_lg = &sbi->s_locality_groups[raw_smp_processor_id()];
Thanks,
Rusty.
next reply other threads:[~2008-09-28 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 1:56 Rusty Russell [this message]
2008-09-28 4:01 ` Unusual code in mballoc.c Eric Sandeen
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=200809281156.12688.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=alex@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=travis@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.