linux-kernel - [PATCH] xen-pciback patches for 3.2 (s/spinlock/mutex/)

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: <1316644966-19386-1-git-send-email-konrad.wilk@oracle.com>
Date:	Wed, 21 Sep 2011 18:42:44 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	jbeulich@...e.com, linux-kernel@...r.kernel.org,
	xen-devel@...ts.xensource.com
Subject: [PATCH] xen-pciback patches for 3.2 (s/spinlock/mutex/)

402c5e1 xen/pciback: miscellaneous adjustments
04df355 xen/pciback: use mutex rather than spinlock in passthrough backend
5fa9991 xen/pciback: use resource_size()

which I've in the stable/drivers.bugfixes on oss.oracle.com
(git://oss.oracle.com/git/kwilk/xen.git) I am proposing these
two patches.

The easier of them: 
  xen/pciback: use mutex rather than spinlock in vpci backend

converts the vpci backend to use the same mechanism as the passthrough backend.

 xen/pciback: Use mutexes when working with Xenbus state transitions.

converts the spinlocks that are guarding the Xenbus state changes to be
mutexs and moves them out to be in similar locations as in the 2.6.18 tree.

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