Thread (7 messages) 7 messages, 3 authors, 2013-01-27

[PATCH 11/19] regmap: avoid undefined return from regmap_read_debugfs

From: arnd@arndb.de (Arnd Bergmann)
Date: 2013-01-26 09:17:39
Also in: lkml

Possibly related (same subject, not in this thread)

On Saturday 26 January 2013, Mark Brown wrote:
On Fri, Jan 25, 2013 at 02:14:28PM +0000, Arnd Bergmann wrote:
quoted
Gcc warns about the case where regmap_read_debugfs tries
Are you sure about that function name?
Yes, regmap_read_debugfs uses the return value from
regmap_debugfs_get_dump_start, for which gcc found
a path that returns the uninitialized value.
quoted
to walk an empty map->debugfs_off_cache list, which results
in uninitialized variable getting returned.
quoted
Setting this variable to 0 first avoids the warning and
the potentially undefined value.
This probably won't apply against current code as there's already a
better fix there, in general just picking a value to initialise masks
errors.
I agree on the general rule not to do this, and I'm trying to avoid it
in the cases where I can find a better fix, but here I could not
(mostly because I could not figure out what this code actually
does. Thanks for taking a look.

Which code is the current version? Is your fix headed for 3.8 inclusion?

I still see the warning in 3.8-rc5 as well as yesterday's linux-next,
with gcc-4.6, 4.7 and 4.8-pre.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help