linux-kernel - [GIT]: Sparc

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: <20100104.232835.124284338.davem@davemloft.net>
Date:	Mon, 04 Jan 2010 23:28:35 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	torvalds@...ux-foundation.org
CC:	akpm@...ux-foundation.org, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [GIT]: Sparc


Fix some fundamental perf issues that were undiscovered until perf top
started using rate based profiling by default.

Fix a crash in bbc_envctrl on unload if kthread_run() fails during
load.  Still need to figure out why kthread_run() is erroring out
though...

Please pull, thanks a lot!

The following changes since commit c5974b835a909ff15c3b7e6cf6789b5eb919f419:
  Linus Torvalds (1):
        Merge branch 'limits_cleanup' of git://decibel.fi.muni.cz/~xslaby/linux

are available in the git repository at:

  master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6.git master

David S. Miller (4):
      bbc_envctrl: Clean up properly if kthread_run() fails.
      Merge branch 'master' of /home/davem/src/GIT/linux-2.6/
      sparc64: Fix NMI programming when perf events are active.
      sparc64: Fix Niagara2 perf event handling.

 arch/sparc/kernel/nmi.c         |    3 +-
 arch/sparc/kernel/perf_event.c  |   11 +++++++
 drivers/sbus/char/bbc_envctrl.c |   64 +++++++++++++++++++++++----------------
 3 files changed, 51 insertions(+), 27 deletions(-)
--
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/