From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Nikita Shubin <NShubin@topcon.com>
Cc: Nikita Shubin <NShubin@topcon.com>, stable@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v4] remoteproc: Fix NULL pointer dereference in rproc_virtio_notify
Date: Sat, 07 Mar 2020 23:20:29 +0000 [thread overview]
Message-ID: <20200307232030.6DEA62075B@mail.kernel.org> (raw)
In-Reply-To: <20200306070325.15232-1-NShubin@topcon.com>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 7a186941626d ("remoteproc: remove the single rpmsg vdev limitation").
The bot has tested the following trees: v5.5.8, v5.4.24, v4.19.108, v4.14.172, v4.9.215, v4.4.215.
v5.5.8: Build OK!
v5.4.24: Build OK!
v4.19.108: Failed to apply! Possible dependencies:
086d08725d34 ("remoteproc: create vdev subdevice with specific dma memory pool")
eb30596eae94 ("remoteproc: add rproc_va_to_pa function")
v4.14.172: Failed to apply! Possible dependencies:
086d08725d34 ("remoteproc: create vdev subdevice with specific dma memory pool")
eb30596eae94 ("remoteproc: add rproc_va_to_pa function")
v4.9.215: Failed to apply! Possible dependencies:
086d08725d34 ("remoteproc: create vdev subdevice with specific dma memory pool")
2b45cef5868a ("remoteproc: Further extend the vdev life cycle")
a863af5d4193 ("remoteproc: virtio: Anchor vring life cycle in vdev")
aab8d8022304 ("remoteproc: Assign kref to rproc_vdev")
eb30596eae94 ("remoteproc: add rproc_va_to_pa function")
f5bcb35387ef ("remoteproc: Decouple vdev resources and devices")
v4.4.215: Failed to apply! Possible dependencies:
086d08725d34 ("remoteproc: create vdev subdevice with specific dma memory pool")
2b45cef5868a ("remoteproc: Further extend the vdev life cycle")
353861660aa2 ("remoteproc: core: Trivial: Improve error checking, spelling and debug prints")
3d87fa1d47c1 ("remoteproc: core: Task sync during rproc_fw_boot()")
9c219b2337b8 ("remoteproc: core: Ensure error message is clear")
a863af5d4193 ("remoteproc: virtio: Anchor vring life cycle in vdev")
aab8d8022304 ("remoteproc: Assign kref to rproc_vdev")
b35d7afc3ba9 ("remoteproc: Calculate max_notifyid during load")
d81fb32f3da6 ("remoteproc: Move vdev handling to boot/shutdown")
ddf711872c9d ("remoteproc: Introduce auto-boot flag")
eb30596eae94 ("remoteproc: add rproc_va_to_pa function")
f5bcb35387ef ("remoteproc: Decouple vdev resources and devices")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-03-07 23:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 11:08 [PATCH] remoteproc: error on kick missing nikita.shubin
2020-02-28 11:08 ` nikita.shubin
2020-03-02 17:44 ` Mathieu Poirier
2020-03-02 21:43 ` Bjorn Andersson
2020-03-02 21:43 ` Bjorn Andersson
2020-03-03 15:56 ` Mathieu Poirier
2020-03-04 14:09 ` nikita.shubin
2020-03-04 16:11 ` Mathieu Poirier
2020-03-05 11:02 ` [PATCH v3 0/1] remoteproc: Fix NULL pointer dereference in rproc_virtio_notify Nikita Shubin
2020-03-05 11:02 ` Nikita Shubin
2020-03-05 11:02 ` [PATCH v3 1/1] " Nikita Shubin
2020-03-05 11:02 ` Nikita Shubin
2020-03-06 7:03 ` [PATCH v4] " Nikita Shubin
2020-03-06 7:03 ` Nikita Shubin
2020-03-06 7:24 ` [PATCH v5] " Nikita Shubin
2020-03-06 7:24 ` Nikita Shubin
2020-03-07 23:20 ` Sasha Levin
2020-03-09 14:22 ` Arnaud POULIQUEN
2020-03-09 14:22 ` Arnaud POULIQUEN
2020-03-10 12:08 ` Nikita Shubin
2020-03-10 13:19 ` Arnaud POULIQUEN
2020-03-10 13:19 ` Arnaud POULIQUEN
2020-03-11 20:01 ` Bjorn Andersson
2020-03-11 20:01 ` Bjorn Andersson
2020-03-16 16:55 ` Mathieu Poirier
2020-03-17 14:24 ` Arnaud POULIQUEN
2020-03-21 17:57 ` Bjorn Andersson
2020-03-21 17:57 ` Bjorn Andersson
2020-03-26 5:46 ` patchwork-bot+linux-remoteproc
2020-03-07 23:20 ` Sasha Levin [this message]
2020-03-07 23:20 ` [PATCH v3 1/1] " Sasha Levin
2020-03-26 5:47 ` [PATCH] remoteproc: error on kick missing patchwork-bot+linux-remoteproc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200307232030.6DEA62075B@mail.kernel.org \
--to=sashal@kernel.org \
--cc=NShubin@topcon.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.