diff options
| author | Adam Wallis <awallis@codeaurora.org> | 2017-11-02 08:53:30 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-11-21 09:49:20 +0100 |
| commit | 34c45c1ee883d080f2fc9a668714ae317c952f6b (patch) | |
| tree | eec711c2c6fadd19ef8fa5aa425a88b032948c57 | |
| parent | 5806ddd7948cc14b8d4b04e25b2831b37fee720d (diff) | |
| download | linux-stable-34c45c1ee883d080f2fc9a668714ae317c952f6b.tar.gz linux-stable-34c45c1ee883d080f2fc9a668714ae317c952f6b.tar.bz2 linux-stable-34c45c1ee883d080f2fc9a668714ae317c952f6b.zip | |
dmaengine: dmatest: warn user when dma test times out
commit a9df21e34b422f79d9a9fa5c3eff8c2a53491be6 upstream.
Commit adfa543e7314 ("dmatest: don't use set_freezable_with_signal()")
introduced a bug (that is in fact documented by the patch commit text)
that leaves behind a dangling pointer. Since the done_wait structure is
allocated on the stack, future invocations to the DMATEST can produce
undesirable results (e.g., corrupted spinlocks). Ideally, this would be
cleaned up in the thread handler, but at the very least, the kernel
is left in a very precarious scenario that can lead to some long debug
sessions when the crash comes later.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197605
Signed-off-by: Adam Wallis <awallis@codeaurora.org>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| -rw-r--r-- | drivers/dma/dmatest.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/dma/dmatest.c b/drivers/dma/dmatest.c index 34ff53290b03..47edc7fbf91f 100644 --- a/drivers/dma/dmatest.c +++ b/drivers/dma/dmatest.c @@ -702,6 +702,7 @@ static int dmatest_func(void *data) * free it this time?" dancing. For now, just * leave it dangling. */ + WARN(1, "dmatest: Kernel stack may be corrupted!!\n"); dmaengine_unmap_put(um); result("test timed out", total_tests, src_off, dst_off, len, 0); |