object.c: do not set ti_old->cset to NULL

During creation, ti_create_and_init accept cset as parameter. So the trigger can use this operation in some way. So, we cannot set to null ti_old->cset because the trigger can use it again Signed-off-by: Federico Vaga <federico.vaga@gmail.com> Acked-by: Alessandro Rubini <rubini@gnudd.com>

object.c: do not set ti_old->cset to NULL
During creation, ti_create_and_init accept cset as parameter. So the trigger can use this operation in some way. So, we cannot set to null ti_old->cset because the trigger can use it again Signed-off-by: Federico Vaga <federico.vaga@gmail.com> Acked-by: Alessandro Rubini <rubini@gnudd.com>
9c35166d · Federico Vaga · Alessandro Rubini · 901df90c · 9c35166d
Commit 9c35166d authored Jan 22, 2013 by Federico Vaga Committed by Alessandro Rubini Jan 25, 2013
Hide whitespace changes
Inline Side-by-side

Showing with 0 additions and 1 deletion

objects.c objects.c +0 -1

No files found.
--- a/objects.c
+++ b/objects.c
@@ -306,7 +306,6 @@ int zio_change_current_trigger(struct zio_cset *cset, char *name)

 	/* Ok, we are done. Kill the current trigger to replace it*/
 	zio_trigger_abort_disable(cset, 1);
-	ti_old->cset = NULL;
 	__ti_unregister(trig_old, ti_old);
 	__ti_destroy(trig_old, ti_old);
 	zio_trigger_put(trig_old, cset->zdev->owner);