On Fri, Nov 20, 2015 at 06:35:42PM -0500, James Simmons wrote:
> @@ -1577,15 +1578,20 @@ static int mdc_ioc_changelog_send(struct obd_device *obd,
> * New thread because we should return to user app before
> * writing into our pipe
> */
> - rc = PTR_ERR(kthread_run(mdc_changelog_send_thread, cs,
> - "mdc_clg_send_thread"));
> - if (!IS_ERR_VALUE(rc)) {
> - CDEBUG(D_CHANGELOG, "start changelog thread\n");
> - return 0;
> + task = kthread_run(mdc_changelog_send_thread, cs,
> + "mdc_clg_send_thread");
> + if (IS_ERR(task)) {
> + rc = PTR_ERR(task);
> + CERROR("%s: can't start changelog thread: rc = %d\n",
> + obd->obd_name, rc);
> + kfree(cs);
> + } else {
> + rc = 0;
> + CDEBUG(D_CHANGELOG, "%s: started changelog thread\n",
> + obd->obd_name);
> }
>
> CERROR("Failed to start changelog thread: %d\n", rc);
> - kfree(cs);
> return rc;
> }
>
This will print an error when it succeeds.
It better to keep the error path and the success path as separate as
possible. For the normal case, the success path is at indent level 1
and the fail path is at indent level 2. Like this:
ret = one();
if (ret)
return ret;
ret = two();
if (ret)
return ret;
return 0;
When it's written that way it is:
success;
if (ret)
fail_path;
success;
if (ret)
fail_path;
success;
The current code looks like:
success;
if (ret) {
fail;
} else {
success;
}
mixed;
You see what I mean? Ideally the function should look like a list of
directives in a row at indent level 1 with only minimal indenting for
errors.
regards,
dan carpenter
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
