This is a note to let you know that I've just added the patch titled
dca: check against empty dca_domains list before unregister provider
to the 3.0-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
dca-check-against-empty-dca_domains-list-before-unregister-provider.patch
and it can be found in the queue-3.0 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From c419fcfd071cf34ba00f9f65282583772d2655e7 Mon Sep 17 00:00:00 2001
From: Maciej Sosnowski <maciej.sosnowski@xxxxxxxxx>
Date: Wed, 23 May 2012 17:27:07 +0200
Subject: dca: check against empty dca_domains list before unregister provider
From: Maciej Sosnowski <maciej.sosnowski@xxxxxxxxx>
commit c419fcfd071cf34ba00f9f65282583772d2655e7 upstream.
When providers get blocked unregister_dca_providers() is called ending up
with dca_providers and dca_domain lists emptied. Dca should be prevented from
trying to unregister any provider if dca_domain list is found empty.
Reported-by: Jiang Liu <jiang.liu@xxxxxxxxxx>
Tested-by: Gaohuai Han <hangaohuai@xxxxxxxxxx>
Signed-off-by: Maciej Sosnowski <maciej.sosnowski@xxxxxxxxx>
Signed-off-by: Dan Williams <djbw@xxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/dca/dca-core.c | 5 +++++
1 file changed, 5 insertions(+)
--- a/drivers/dca/dca-core.c
+++ b/drivers/dca/dca-core.c
@@ -409,6 +409,11 @@ void unregister_dca_provider(struct dca_
spin_lock_irqsave(&dca_lock, flags);
+ if (list_empty(&dca_domains)) {
+ raw_spin_unlock_irqrestore(&dca_lock, flags);
+ return;
+ }
+
list_del(&dca->node);
pci_rc = dca_pci_rc_from_dev(dev);
Patches currently in stable-queue which might be from maciej.sosnowski@xxxxxxxxx are
queue-3.0/dca-check-against-empty-dca_domains-list-before-unregister-provider.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html