linux-kernel - [GIT PULL] kgdb regression fixes for 2.6.33

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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1264719883-7285-1-git-send-email-jason.wessel@windriver.com>
Date:	Thu, 28 Jan 2010 17:04:41 -0600
From:	Jason Wessel <jason.wessel@...driver.com>
To:	torvalds@...ux-foundation.org
Cc:	linux-kernel@...r.kernel.org, kgdb-bugreport@...ts.sourceforge.net
Subject: [GIT PULL]  kgdb regression fixes for 2.6.33

Linus, please pull the kgdb git tree fixes for 2.6.33-rc5

  git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus

Summary:
  
  * Fix the kgdb regression in functionality caused by the new hw
    breakpoint API changes in 2.6.33.

This leaves us with some cleanup in 2.6.34, but all the previous
functionality works again.  In fact you can use hw breakpoints in user
space and the kernel at the same time now that the API is shared,
which is something that never previously worked.

Thanks,
Jason.

--
The following changes since commit be8cde8b24c9dca1e54598690115eee5b1476519:
  Linus Torvalds (1):
        Merge git://git.kernel.org/.../jejb/scsi-rc-fixes-2.6

--
Jason Wessel (2):
      x86,hw_breakpoint,kgdb: kgdb to use hw_breakpoint API
      perf,hw_breakpoint,kgdb: No mutex taken for kernel debugger

 arch/x86/kernel/kgdb.c        |  222 ++++++++++++++++++++++++++++++-----------
 include/linux/hw_breakpoint.h |    2 +
 kernel/hw_breakpoint.c        |   52 ++++++++--
 kernel/kgdb.c                 |    3 +
 4 files changed, 212 insertions(+), 67 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/