linux-kernel - [PATCH] Fixes to Linux v3.13 - bugs.xenproject.org ones. (v1).

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]

Date:	Fri,  8 Nov 2013 12:38:02 -0500
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Ian.Campbell@...rix.com, xen-devel@...ts.xenproject.org,
	linux-kernel@...r.kernel.org, JBeulich@...e.com,
	david.vrabel@...rix.com, boris.ostrovsky@...cle.com
Subject: [PATCH] Fixes to Linux v3.13 - bugs.xenproject.org ones. (v1).

Hey,

Two of these:
 [PATCH 2/4] xen/manage: Poweroff forcefully if user-space is not yet
 [PATCH 4/4] xen/xenbus: Avoid synchronous wait on XenBus stalling

fix the bugs.xenproject.org outstanding bugs.

The other ones are that were discovered on xen-devel and discussed.
They should go in v3.13 and as the merge window is next week I am
hoping they can be squeezed in then.


 drivers/xen/manage.c            | 64 ++++++++++++++++++++++++++++++++++-------
 drivers/xen/pci.c               | 47 ++++++++++++++++++++++++++++++
 drivers/xen/xenbus/xenbus_xs.c  | 24 ++++++++++++++--
 include/xen/interface/physdev.h | 11 +++++++
 
Konrad Rzeszutek Wilk (4):
      xen/mcfg: Call PHYSDEVOP_pci_mmcfg_reserved for MCFG areas.
      xen/manage: Poweroff forcefully if user-space is not yet up.
      xen/manage: Guard against user-space initiated poweroff and XenBus.
      xen/xenbus: Avoid synchronous wait on XenBus stalling shutdown/restart.

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