The patch titled
pata_legacy: fix no device fail path
has been added to the -mm tree. Its filename is
pata_legacy-fix-no-device-fail-path.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: pata_legacy: fix no device fail path
From: Tejun Heo <htejun@xxxxxxxxx>
When pata_legacy can't detect any device, it unregisters the
platform_device and fails detection. However, it forgets to detach ata
host triggering weird failures as the host later gets freed by devres
while still attached. Fix it.
Signed-off-by: Tejun Heo <tj@xxxxxxxxxx>
Reported-by: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Cc: Jeff Garzik <jeff@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/ata/pata_legacy.c | 1 +
1 file changed, 1 insertion(+)
diff -puN drivers/ata/pata_legacy.c~pata_legacy-fix-no-device-fail-path drivers/ata/pata_legacy.c
--- a/drivers/ata/pata_legacy.c~pata_legacy-fix-no-device-fail-path
+++ a/drivers/ata/pata_legacy.c
@@ -1032,6 +1032,7 @@ static __init int legacy_init_one(struct
return 0;
}
}
+ ata_host_detach(host);
fail:
platform_device_unregister(pdev);
return ret;
_
Patches currently in -mm which might be from htejun@xxxxxxxxx are
linux-next.patch
pata_legacy-fix-no-device-fail-path.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
