3.2-stable review patch.  If anyone has any objections, please let me know.

------------------

From: Zeev Tarantov <[email protected]>

[Patch not needed upstream as this is a backport build bugfix - gregkh

gcc correctly complains:

util/hist.c: In function ‘__hists__add_entry’:
util/hist.c:240:27: error: invalid type argument of ‘->’ (have ‘struct 
hist_entry’)
util/hist.c:241:23: error: invalid type argument of ‘->’ (have ‘struct 
hist_entry’)

for this new code:

+                       if (he->ms.map != entry->ms.map) {
+                               he->ms.map = entry->ms.map;
+                               if (he->ms.map)
+                                       he->ms.map->referenced = true;
+                       }

because "entry" is a "struct hist_entry", not a pointer to a struct.

In mainline, "entry" is a pointer to struct passed as argument to the function.
So this is broken during backporting. But obviously not compile tested.

Signed-off-by: Zeev Tarantov <[email protected]>
Cc: Signed-off-by: David S. Miller <[email protected]>
Cc: Arnaldo Carvalho de Melo <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Signed-off-by: Ben Hutchings <[email protected]>
---
 tools/perf/util/hist.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- a/tools/perf/util/hist.c
+++ b/tools/perf/util/hist.c
@@ -237,8 +237,8 @@ struct hist_entry *__hists__add_entry(st
                         * mis-adjust symbol addresses when computing
                         * the history counter to increment.
                         */
-                       if (he->ms.map != entry->ms.map) {
-                               he->ms.map = entry->ms.map;
+                       if (he->ms.map != entry.ms.map) {
+                               he->ms.map = entry.ms.map;
                                if (he->ms.map)
                                        he->ms.map->referenced = true;
                        }


--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to