From: Dan Carpenter <dan.carpenter@oracle.com>
To: viresh.kumar@linaro.org
Cc: linux-pm@vger.kernel.org
Subject: re: PM / OPP: Add debugfs support
Date: Tue, 22 Sep 2015 15:34:54 +0300 [thread overview]
Message-ID: <20150922123454.GE27407@mwanda> (raw)
Hello Viresh Kumar,
The patch 5cb5fdbf3877: "PM / OPP: Add debugfs support" from Sep 4,
2015, leads to a bunch of static checker warnings:
drivers/base/power/opp/debugfs.c:41 opp_debug_create_one() error: format string overflow. buf_size: 15 length: 24
drivers/base/power/opp/debugfs.c:48 opp_debug_create_one() warn: passing casted pointer '&opp->available' to 'debugfs_create_bool()' 1 vs 32.
drivers/base/power/opp/debugfs.c:52 opp_debug_create_one() warn: passing casted pointer '&opp->dynamic' to 'debugfs_create_bool()' 1 vs 32.
drivers/base/power/opp/debugfs.c:55 opp_debug_create_one() warn: passing casted pointer '&opp->turbo' to 'debugfs_create_bool()' 1 vs 32.
drivers/base/power/opp/debugfs.c:58 opp_debug_create_one() warn: passing casted pointer '&opp->rate' to 'debugfs_create_u32()' 64 vs 32.
drivers/base/power/opp/debugfs.c:61 opp_debug_create_one() warn: passing casted pointer '&opp->u_volt' to 'debugfs_create_u32()' 64 vs 32.
drivers/base/power/opp/debugfs.c:65 opp_debug_create_one() warn: passing casted pointer '&opp->u_volt_min' to 'debugfs_create_u32()' 64 vs 32.
drivers/base/power/opp/debugfs.c:69 opp_debug_create_one() warn: passing casted pointer '&opp->u_volt_max' to 'debugfs_create_u32()' 64 vs 32.
drivers/base/power/opp/debugfs.c:73 opp_debug_create_one() warn: passing casted pointer '&opp->u_amp' to 'debugfs_create_u32()' 64 vs 32.
drivers/base/power/opp/debugfs.c:76 opp_debug_create_one() warn: passing casted pointer '&opp->clock_latency_ns' to 'debugfs_create_u32()' 64 vs 32.
drivers/base/power/opp/debugfs.c
34 int opp_debug_create_one(struct dev_pm_opp *opp, struct device_opp *dev_opp)
35 {
36 struct dentry *pdentry = dev_opp->dentry;
37 struct dentry *d;
38 char name[15];
39
40 /* Rate is unique to each OPP, use it to give opp-name */
41 sprintf(name, "opp:%lu", opp->rate);
opp->rate is unsigned long so the static checker says this can overflow
on 64 bit systems. The static checker tries to do cross function
analysis, but it's actually wrong. There is a later bug which cancels
out this bug.
Anyway, we should make the buffer larger and or change it to use
snprintf().
42
43 /* Create per-opp directory */
44 d = debugfs_create_dir(name, pdentry);
45 if (!d)
46 return -ENOMEM;
47
48 if (!debugfs_create_bool("available", S_IRUGO, d,
49 (u32 *)&opp->available))
debugfs_create_bool() writes 32 bits, but we only have 8 bits of space
so this corrupts memory.
50 return -ENOMEM;
51
52 if (!debugfs_create_bool("dynamic", S_IRUGO, d, (u32 *)&opp->dynamic))
53 return -ENOMEM;
Same.
54
55 if (!debugfs_create_bool("turbo", S_IRUGO, d, (u32 *)&opp->turbo))
56 return -ENOMEM;
Same.
57
58 if (!debugfs_create_u32("rate_hz", S_IRUGO, d, (u32 *)&opp->rate))
59 return -ENOMEM;
This only writes to the first 32 bits of the unsigned long. Which will
not work on big endian systems.
I don't know why is there no debugfs_create_ul() function. It seems
like it wouldn't be that complicated to create one.
It's the same for the rest of this funciton.
regards,
dan carpenter
next reply other threads:[~2015-09-22 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 12:34 Dan Carpenter [this message]
2015-10-08 9:17 ` PM / OPP: Add debugfs support Viresh Kumar
2015-10-08 9:25 ` Dan Carpenter
2015-10-08 11:15 ` Viresh Kumar
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=20150922123454.GE27407@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).