Thread (12 messages) flat view 12 messages, 2 authors, 2012-10-04

RE: [PATCH 3/5] rapidio: run discovery as an asynchronous process

From: Bounine, Alexandre <hidden>
Date: 2012-10-04 19:09:41
Also in: lkml

On Wed, October 03, 2012 6:30 PM
Andrew Morton [off-list ref] wrote:
quoted hunk ↗ jump to hunk
=20
On Wed,  3 Oct 2012 15:18:41 -0400
Alexandre Bounine [off-list ref] wrote:
=20
quoted
...

+static void __devinit disc_work_handler(struct work_struct *_work)
+{
+	struct rio_disc_work *work =3D container_of(_work,
+						  struct rio_disc_work, work);
=20
There's a nice simple way to avoid such ugliness:
=20
--- a/drivers/rapidio/rio.c~rapidio-run-discovery-as-an-asynchronous-
process-fix
+++ a/drivers/rapidio/rio.c
@@ -1269,9 +1269,9 @@ struct rio_disc_work {
=20
 static void __devinit disc_work_handler(struct work_struct *_work)
 {
-	struct rio_disc_work *work =3D container_of(_work,
-						  struct rio_disc_work, work);
+	struct rio_disc_work *work;
=20
+	work =3D container_of(_work, struct rio_disc_work, work);
 	pr_debug("RIO: discovery work for mport %d %s\n",
 		 work->mport->id, work->mport->name);
 	rio_disc_mport(work->mport);
_
=20
Thank you for the fix. Will avoid that ugliness in the future.
quoted
+	pr_debug("RIO: discovery work for mport %d %s\n",
+		 work->mport->id, work->mport->name);
+	rio_disc_mport(work->mport);
+
+	kfree(work);
+}
+
 int __devinit rio_init_mports(void)
 {
 	struct rio_mport *port;
+	struct rio_disc_work *work;
+	int no_disc =3D 0;

 	list_for_each_entry(port, &rio_mports, node) {
 		if (port->host_deviceid >=3D 0)
 			rio_enum_mport(port);
-		else
-			rio_disc_mport(port);
+		else if (!no_disc) {
+			if (!rio_wq) {
+				rio_wq =3D alloc_workqueue("riodisc", 0, 0);
+				if (!rio_wq) {
+					pr_err("RIO: unable allocate rio_wq\n");
+					no_disc =3D 1;
+					continue;
+				}
+			}
+
+			work =3D kzalloc(sizeof *work, GFP_KERNEL);
+			if (!work) {
+				pr_err("RIO: no memory for work struct\n");
+				no_disc =3D 1;
+				continue;
+			}
+
+			work->mport =3D port;
+			INIT_WORK(&work->work, disc_work_handler);
+			queue_work(rio_wq, &work->work);
+		}
+	}
=20
I'm having a lot of trouble with `no_disc'.  afacit what it does is to
cease running async discovery for any remaining devices if the
workqueue
allocation failed (vaguely reasonable) or if the allocation of a single
work item failed (incomprehensible).
=20
But if we don't run discovery, the subsystem is permanently busted for
at least some devices, isn't it?
This is correct. We are considering ways to restart discovery
process later but it is not applicable now.
=20
And this code is basically untestable unless the programmer does
deliberate fault injection, which makes it pretty much unmaintainable.
=20
So...  if I haven't totally misunderstood, I suggest a rethink is in
order?
I will review and simplify. Probably, just try to allocate all required
resources ahead of port list scan. Simple and safe.
=20
quoted
+	if (rio_wq) {
+		pr_debug("RIO: flush discovery workqueue\n");
+		flush_workqueue(rio_wq);
+		pr_debug("RIO: flush discovery workqueue finished\n");
+		destroy_workqueue(rio_wq);
 	}
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help