linux-kernel - [PATCH] small bug-fixes

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: <1299789405-30802-1-git-send-email-konrad.wilk@oracle.com>
Date:	Thu, 10 Mar 2011 15:36:43 -0500
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	linux-kernel@...r.kernel.org,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Stefano Stabellini <stefano.stabellini@...citrix.com>,
	Ian Campbell <Ian.Campbell@...rix.com>
Cc:	xen-devel@...ts.xensource.com,
	Konrad Rzeszutek Wilk <konrad@...nel.org>
Subject: [PATCH] small bug-fixes

During testing (git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git #linux-next)

I found that ballooning of PV guests stopped working and traced it down to
2f14ddc3a7146ea4cd5a3d1ecd993f85f2e4f948
"xen/setup: Inhibit resource API from using System RAM E820 gaps as PCI mem gaps"
which is correct for the initial domain, but not for true PV guests. This patch:

 "xen/e820: Don't mark balloon memory as E820_UNUSABLE when running as guest."
   fixes that.

The second I found when running 2.6.32 pvops tree when we swapped over from
using level_irq handler for VIRQ to percpu irq handler. There is a race window
that I was able to hit 66% of time. With 2.6.38 I can't seem to hit this and I am
not sure why - but it still makes sense to add this patch in. The patch in
question is:

 xen/hvc: Disable probe_irq_on/off from poking the hvc-console IRQ line.

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