linux-kernel - [GIT PULL] arm64 perf fixes for 3.11

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20130820172245.GA23603@arm.com>
Date:	Tue, 20 Aug 2013 18:22:51 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: [GIT PULL] arm64 perf fixes for 3.11

Hi Linus,

Late pull request for arm64 perf fixes (similar to the recent arm perf
patches). Thanks.


The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:

  Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git tags/arm64-stable

for you to fetch changes up to ee7538a008a45050c8f706d38b600f55953169f9:

  arm64: perf: fix event validation for software group leaders (2013-08-20 12:05:57 +0100)

----------------------------------------------------------------
Perf backend fixes for arm64 where the user can cause kernel panic
(discovered with Vince's fuzzing tool).

----------------------------------------------------------------
Will Deacon (2):
      arm64: perf: fix array out of bounds access in armpmu_map_hw_event()
      arm64: perf: fix event validation for software group leaders

 arch/arm64/kernel/perf_event.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

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