linux-kernel - [GIT PULL] (xen) stable/bug.fixes for 3.1-rc5.

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: <20110906161046.GA5548@dumpdata.com>
Date:	Tue, 6 Sep 2011 12:10:46 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Cc:	david.vrabel@...rix.com, imammedo@...hat.com,
	Ian.Campbell@...citrix.com
Subject: [GIT PULL] (xen) stable/bug.fixes for 3.1-rc5.

Hey Linus,

Please git pull the following branch from my backup git server:

git pull git://oss.oracle.com/git/kwilk/xen.git stable/bug.fixes

It is based off git commit 60c5f08e154fd235056645e050f2cd5671b19125
Jeremy Fitzhardinge (1):
    xen/tracing: Fix tracing config option properly

Which you pulled in earlier (3.1-rc3?).

We got some ecstatic bug-fixes - one in particular has been in the tree since 2.6.27!
They are (in order of "oh-my-what-a-bug"):
 1). Don't enable the interrupts when a page fault has occurred - this ended up triggering
     when we were executing a IRQ handler and re-enabling the IRQ line!
 2). Respect the dom0_mem=max:X argument that the hypervisor can use to limit the amount
     of memory the initial Linux kernel would use. Without it, on largish (32GB>) the
     initial domain had tons of unused 'struct page' that were never going to be used.
 3). Lastly, print out a warning when the user uses specific Linux kernel parameters
     that we cannot handle ("nosmp" or "noapic").

The credit list is:

David Vrabel (1):
      xen: use maximum reservation to limit amount of usable RAM

Igor Mammedov (1):
      xen: x86_32: do not enable iterrupts when returning from exception in interrupt context

Konrad Rzeszutek Wilk (1):
      xen/smp: Warn user why they keel over - nosmp or noapic and what to use instead.

Diff stat:

 arch/x86/xen/setup.c      |   19 +++++++++++++++++++
 arch/x86/xen/smp.c        |   10 ++++++++++
 arch/x86/xen/xen-asm_32.S |    8 +++++---
 3 files changed, 34 insertions(+), 3 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/