Re: [GIT PULL 0/4] perf/urgent fixes

From: Ingo Molnar
Date: Fri Jul 10 2015 - 04:04:53 EST



* Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> wrote:

> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit ebf2d2689de551d90965090bb991fc640a0c0d41:
>
> perf/x86: Fix copy_from_user_nmi() return if range is not ok (2015-07-06 14:09:27 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo
>
> for you to fetch changes up to 08ae217b8d44986062fe3648c5bb83816d5bc00f:
>
> perf thread_map: Fix the sizeof() calculation for map entries (2015-07-09 12:28:53 -0300)
>
> ----------------------------------------------------------------
> perf/urgent fixes:
>
> User visible:
>
> - Fix 'perf top -u username', where not enough memory per thread_map
> entry was being allocated nor was being initialized, causing a
> segfault (Arnaldo Carvalho de Melo)
>
> - Fix locking lockup using 32-bit compat vdso (Adrian Hunter)
>
> Developer stuff:
>
> - Fix shadow declaration of close with older build environments (Jiri Olsa)
>
> - Make the 'clean' target do a better job, removing some more
> temp files (Riku Voipio)
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
>
> ----------------------------------------------------------------
> Adrian Hunter (1):
> perf tools: Fix lockup using 32-bit compat vdso
>
> Arnaldo Carvalho de Melo (1):
> perf thread_map: Fix the sizeof() calculation for map entries
>
> Jiri Olsa (1):
> perf stat: Fix shadow declaration of close
>
> Riku Voipio (1):
> tools lib: Improve clean target
>
> tools/lib/api/Makefile | 2 +-
> tools/lib/traceevent/Makefile | 2 +-
> tools/perf/builtin-stat.c | 4 ++--
> tools/perf/util/thread_map.c | 3 +--
> tools/perf/util/vdso.c | 8 +++-----
> 5 files changed, 8 insertions(+), 11 deletions(-)

Pulled this and the second round of fixes, thanks a lot Arnaldo!

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/