linux-kernel - [PATCH 0/3] KGDB/KDB/UV: Fixups for UV to KGDB interface

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: <20140114162551.093907830@asylum.americas.sgi.com>
Date:	Tue, 14 Jan 2014 10:25:51 -0600
From:	Mike Travis <travis@....com>
To:	Ingo Molnar <mingo@...hat.com>,
	Jason Wessel <jason.wessel@...driver.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Hedi Berriche <hedi@....com>, Russ Anderson <rja@....com>,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] KGDB/KDB/UV: Fixups for UV to KGDB interface

v2: Update patch 2/3 to include which problems fixed.  Other minor
  changes detailed in the patches.

* 1/3: Change the fix for 'KDB not defined' build problem by changing
  the kgdb_nmicallin() interface to include the KDB specific reason code.
  This removes the dependency on KDB in the debug core.  It also requires
  a change to the kgdb call in from UV NMI handler to avoid a compile
  error.

* 2/3: Fix problems found by the kbuild test robot tip-bot:
  Make uv_register_nmi_notifier() and uv_handle_nmi_ping() static to
  address sparse warnings.  Fix problem where uv_nmi_kexec_failed is
  unused when CONFIG_KEXEC is not defined.

* 3/3: Fix UV call into kgdb to depend only on whether KGDB is defined
  and not both KGDB and KDB.  This allows the power nmi command to
  use the gdb remote connection if enabled.  Note new action of 'kgdb'
  needs to be set as well to indicate user wants the kernel to wait for
  gdb to be connected.  If it's set to 'kdb' then an error message is
  displayed if KDB is not configured.

  Also note that if both KGDB and KDB are enabled, then the action
  of 'kgdb' or 'kdb' has no affect on which is used.  See the KGDB
  documentation for further information.
--

-- 
--
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/