[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220216081224.9956-3-p-mohan@ti.com>
Date: Wed, 16 Feb 2022 13:42:24 +0530
From: Puranjay Mohan <p-mohan@...com>
To: <kishon@...com>, <vigneshr@...com>, <s-anna@...com>,
<bjorn.andersson@...aro.org>, <mathieu.poirier@...aro.org>,
<linux-remoteproc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
CC: Puranjay Mohan <p-mohan@...com>
Subject: [PATCH v5 2/2] remoteproc: wkup_m3: Set sysfs_read_only flag
From: Suman Anna <s-anna@...com>
The Wakeup M3 remote processor is controlled by the wkup_m3_ipc
client driver, so set the newly introduced 'sysfs_read_only' flag
to not allow any overriding of the remoteproc firmware, state,
recovery, or coredump from userspace.
Signed-off-by: Suman Anna <s-anna@...com>
Signed-off-by: Puranjay Mohan <p-mohan@...com>
Reviewed-by: Mathieu Poirier <mathieu.poirier@...aro.org>
---
Changes in v4->v5
rename deny_sysfs_ops to sysfs_read_only
---
drivers/remoteproc/wkup_m3_rproc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/remoteproc/wkup_m3_rproc.c b/drivers/remoteproc/wkup_m3_rproc.c
index 484f7605823e..a0c204cb0979 100644
--- a/drivers/remoteproc/wkup_m3_rproc.c
+++ b/drivers/remoteproc/wkup_m3_rproc.c
@@ -163,6 +163,7 @@ static int wkup_m3_rproc_probe(struct platform_device *pdev)
}
rproc->auto_boot = false;
+ rproc->sysfs_read_only = true;
wkupm3 = rproc->priv;
wkupm3->rproc = rproc;
--
2.17.1
Powered by blists - more mailing lists