Hi Peter,
Basically if running a TPM command with a long enough duration (>
timeout_c), the answer will never be read correctly.
This only appear if using irq mode.
I am actually doing the backport to james tree at the moment and will
send it later on tonight.
I will send this directly without including stable@...
Best Regards
Christophe
On 19/03/2015 22:34, Peter Hüwe wrote:
Hi,
great timing :) I just sent the pull request for 4.1 out yesterday :)
But thanks for spotting and fixing it.
Found bugs are good bugs, and fixed ones are even better.
Am Donnerstag, 19. März 2015, 22:15:08 schrieb Christophe Ricard:
Hi,
Please find in this patch a fix that fix an improper command completion
wait. This patch apply on top of for-james branch
tpm/tpm_infineon: Use struct dev_pm_ops for power management
6b37729bd184fdd44f144c6cc4951b06b55bcf4b
*** Note: This bug is also present in kernel 4.0 but will not apply as the
driver structure changed between kernel 4.0 and kernel 4.1.
A backported version is also going to be sent to <stable@xxxxxxxxxxxxxxx> ?
Are kernels < 4.0 also affected or was this code introduced in 4.0 ?
How critical is the mentioned 'critical failure' ? What will happen?
How often does it happen?
If this thing is big enough and kernels < 4.0 are not affected we can try to
get it into 4.0 still, so no stable. (but I still need the backport :) )
If it won't hit 4.0 then backport to 4.0.1 is needed,
which will be sent to stable@...
with the upstream commit mentioned.
See
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/stable_kernel_rules.txt
Thanks,
Peter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
