lkml.org 
[lkml]   [2020]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH v3 06/15] remoteproc: Properly deal with a kernel panic when attached
    Date
    The panic handler operation of registered remote processors
    should also be called when remote processors have been
    attached to.

    Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
    Reviewed-by: Peng Fan <peng.fan@nxp.com>
    Reviewed-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>
    ---
    drivers/remoteproc/remoteproc_core.c | 6 +++++-
    1 file changed, 5 insertions(+), 1 deletion(-)

    diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
    index 300785a18f03..539667948bc8 100644
    --- a/drivers/remoteproc/remoteproc_core.c
    +++ b/drivers/remoteproc/remoteproc_core.c
    @@ -2471,7 +2471,11 @@ static int rproc_panic_handler(struct notifier_block *nb, unsigned long event,

    rcu_read_lock();
    list_for_each_entry_rcu(rproc, &rproc_list, node) {
    - if (!rproc->ops->panic || rproc->state != RPROC_RUNNING)
    + if (!rproc->ops->panic)
    + continue;
    +
    + if (rproc->state != RPROC_RUNNING &&
    + rproc->state != RPROC_ATTACHED)
    continue;

    d = rproc->ops->panic(rproc);
    --
    2.25.1
    \
     
     \ /
      Last update: 2020-11-26 22:09    [W:4.742 / U:0.812 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site