From: Paul Jackson <pj@sgi.com>
To: "Paul Menage" <menage@google.com>
Cc: akpm@linux-foundation.org, lizf@cn.fujitsu.com,
seto.hidetoshi@jp.fujitsu.com, mingo@elte.hu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix cpuset sched_relax_domain_level control file
Date: Tue, 6 May 2008 21:32:04 -0500 [thread overview]
Message-ID: <20080506213204.c54b328d.pj@sgi.com> (raw)
In-Reply-To: <6599ad830805061915s2525e48fw369e7c1aff167a76@mail.gmail.com>
Paul M wrote:
> I'm building against 2.6.26-rc1, and don't see those warnings (or any
> useful code at those lines). It's probably more fallout from the
The following error that Andrew reports seems to be another
side affect of the "system" patch to cpusets.
Andrew wrote:
> cpuset files changes?
I see this error too:
kernel/cpuset.c: In function 'cpuset_common_file_write':
kernel/cpuset.c:1374: warning: passing argument 3 of 'update_flag' makes integer from pointer without a cast
kernel/cpuset.c: In function 'cpuset_destroy':
kernel/cpuset.c:1793: warning: passing argument 3 of 'update_flag' makes integer from pointer without a cast
I am building with:
Andrew's latest (last couple hours) mmotm, applied on top of
v2.6.26-rc1, with -just- the first two mmotm patches applied to
v2.6.26-rc1, plus your patch:
origin.patch -- from mmotm
linux-next.patch -- from mmotm
Your recent "Fix cpuset sched_relax_domain_level control file" patch
The warning comes from the type inconsistence between the following
lines of kernel/cpuset.c code. The definition of update_flag() is
expecting an "int turning_on" third argument. The borked "system"
patch (on my wish I could kill it list) is providing a "char *"
argument.
static int update_flag(cpuset_flagbits_t bit, struct cpuset *cs,
int turning_on)
...
static ssize_t cpuset_common_file_write(struct cgroup *cont,
struct cftype *cft,
struct file *file,
const char __user *userbuf,
size_t nbytes, loff_t *unused_ppos)
{
struct cpuset *cs = cgroup_cs(cont);
cpuset_filetype_t type = cft->private;
char *buffer;
int retval = 0;
...
case FILE_SYSTEM:
retval = update_flag(CS_SYSTEM, cs, buffer);
...
if (!is_system(cs))
update_flag(CS_SYSTEM, cs, "1");
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-05-07 2:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 1:08 Paul Menage
2008-05-07 1:21 ` Li Zefan
2008-05-07 1:31 ` Andrew Morton
2008-05-07 1:40 ` Paul Jackson
2008-05-07 3:38 ` Reverting per-cpuset "system" (IRQ affinity) patch (was: Fix cpuset sched_relax_domain_level control file) Paul Jackson
2008-05-07 3:44 ` Andrew Morton
2008-05-07 3:52 ` Paul Jackson
2008-05-07 6:44 ` Peter Zijlstra
2008-05-08 17:56 ` Reverting per-cpuset "system" (IRQ affinity) patch Max Krasnyansky
2008-05-09 10:22 ` Ingo Molnar
2008-05-09 11:26 ` Paul Jackson
2008-05-21 0:46 ` Max Krasnyanskiy
2008-05-07 1:38 ` [PATCH] Fix cpuset sched_relax_domain_level control file Andrew Morton
2008-05-07 1:41 ` Paul Menage
2008-05-07 9:48 ` Adrian Bunk
2008-05-07 15:08 ` Andrew Morton
2008-05-07 1:46 ` Li Zefan
2008-05-07 1:49 ` Paul Jackson
2008-05-07 1:51 ` Paul Menage
2008-05-07 1:58 ` Paul Jackson
2008-05-07 2:08 ` Andrew Morton
2008-05-07 2:11 ` Paul Jackson
2008-05-07 2:15 ` Paul Menage
2008-05-07 2:28 ` Andrew Morton
2008-05-07 2:32 ` Paul Jackson [this message]
2008-05-07 2:12 ` Li Zefan
2008-05-07 2:17 ` Paul Jackson
2008-05-07 2:27 ` Hidetoshi Seto
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=20080506213204.c54b328d.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=seto.hidetoshi@jp.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
Powered by JetHome