From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Puranjay Mohan <p-mohan@ti.com>
Cc: vigneshr@ti.com, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kishon Vijay Abraham I <kishon@ti.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [EXTERNAL] Re: [PATCH v5 1/2] remoteproc: Introduce sysfs_read_only flag
Date: Fri, 4 Mar 2022 09:53:46 -0700 [thread overview]
Message-ID: <20220304165346.GA1646337@p14s> (raw)
In-Reply-To: <869aa1ad-e3ed-cd0b-ab5e-a4b7d1d23311@ti.com>
On Thu, Mar 03, 2022 at 01:30:08PM +0530, Puranjay Mohan wrote:
> Hi Bjorn,
> Hi Mathieu,
>
> When is this series expected to be applied?
>
> I am going to post another series titled "PRU Consumer API".
> One patch from that series depends on this "Introduce sysfs_read_only
> flag" patch.
>
> Please let me know so I can rebase and post that series.
Applied and pushed.
Thanks,
Mathieu
>
> Thanks,
> Puranjay Mohan
>
> On 18/02/22 11:24, Bjorn Andersson wrote:
> > On Thu 17 Feb 21:00 PST 2022, Kishon Vijay Abraham I wrote:
> >
> >>
> >>
> >> On 16/02/22 1:42 pm, Puranjay Mohan wrote:
> >>> The remoteproc framework provides sysfs interfaces for changing
> >>> the firmware name and for starting/stopping a remote processor
> >>> through the sysfs files 'state' and 'firmware'. The 'coredump'
> >>> file is used to set the coredump configuration. The 'recovery'
> >>> sysfs file can also be used similarly to control the error recovery
> >>> state machine of a remoteproc. These interfaces are currently
> >>> allowed irrespective of how the remoteprocs were booted (like
> >>> remoteproc self auto-boot, remoteproc client-driven boot etc).
> >>> These interfaces can adversely affect a remoteproc and its clients
> >>> especially when a remoteproc is being controlled by a remoteproc
> >>> client driver(s). Also, not all remoteproc drivers may want to
> >>> support the sysfs interfaces by default.
> >>>
> >>> Add support to make the remoteproc sysfs files read only by
> >>> introducing a state flag 'sysfs_read_only' that the individual
> >>> remoteproc drivers can set based on their usage needs. The default
> >>> behavior is to allow the sysfs operations as before.
> >>>
> >>> Implement attribute_group->is_visible() to make the sysfs
> >>> entries read only when 'sysfs_read_only' flag is set.
> >>>
> >>> Signed-off-by: Puranjay Mohan <p-mohan@ti.com>
> >>> Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> >>> ---
> >>> Changes in v4->v5:
> >>> Rename deny_sysfs_ops to sysfs_read_only.
> >>> Make coredump readonly with other files.
> >>>
> >>> Changes in v3->v4:
> >>> Use mode = 0444 in rproc_is_visible() to make the sysfs entries
> >>> read-only when the deny_sysfs_ops flag is set.
> >>> ---
> >>> drivers/remoteproc/remoteproc_sysfs.c | 19 ++++++++++++++++++-
> >>> include/linux/remoteproc.h | 2 ++
> >>> 2 files changed, 20 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/remoteproc/remoteproc_sysfs.c b/drivers/remoteproc/remoteproc_sysfs.c
> >>> index ea8b89f97d7b..abf0cd05d5e1 100644
> >>> --- a/drivers/remoteproc/remoteproc_sysfs.c
> >>> +++ b/drivers/remoteproc/remoteproc_sysfs.c
> >>> @@ -230,6 +230,22 @@ static ssize_t name_show(struct device *dev, struct device_attribute *attr,
> >>> }
> >>> static DEVICE_ATTR_RO(name);
> >>>
> >>> +static umode_t rproc_is_visible(struct kobject *kobj, struct attribute *attr,
> >>> + int n)
> >>> +{
> >>> + struct device *dev = kobj_to_dev(kobj);
> >>> + struct rproc *rproc = to_rproc(dev);
> >>> + umode_t mode = attr->mode;
> >>> +
> >>> + if (rproc->sysfs_read_only && (attr == &dev_attr_recovery.attr ||
> >>> + attr == &dev_attr_firmware.attr ||
> >>> + attr == &dev_attr_state.attr ||
> >>> + attr == &dev_attr_coredump.attr))
> >>> + mode = 0444;
> >>
> >> Nitpick: use S_IRUGO instead of 0444.
> >>
> >
> > Thanks for the suggestion Kishon, but I like 0444, it has direct meaning
> > to me.
> >
> > So unless there's some directive to use S_I*** throughout the kernel I
> > would prefer this.
> >
> > Regards,
> > Bjorn
> >
> >> Thanks,
> >> Kishon
> >>> +
> >>> + return mode;
> >>> +}
> >>> +
> >>> static struct attribute *rproc_attrs[] = {
> >>> &dev_attr_coredump.attr,
> >>> &dev_attr_recovery.attr,
> >>> @@ -240,7 +256,8 @@ static struct attribute *rproc_attrs[] = {
> >>> };
> >>>
> >>> static const struct attribute_group rproc_devgroup = {
> >>> - .attrs = rproc_attrs
> >>> + .attrs = rproc_attrs,
> >>> + .is_visible = rproc_is_visible,
> >>> };
> >>>
> >>> static const struct attribute_group *rproc_devgroups[] = {
> >>> diff --git a/include/linux/remoteproc.h b/include/linux/remoteproc.h
> >>> index e0600e1e5c17..93a1d0050fbc 100644
> >>> --- a/include/linux/remoteproc.h
> >>> +++ b/include/linux/remoteproc.h
> >>> @@ -523,6 +523,7 @@ struct rproc_dump_segment {
> >>> * @table_sz: size of @cached_table
> >>> * @has_iommu: flag to indicate if remote processor is behind an MMU
> >>> * @auto_boot: flag to indicate if remote processor should be auto-started
> >>> + * @sysfs_read_only: flag to make remoteproc sysfs files read only
> >>> * @dump_segments: list of segments in the firmware
> >>> * @nb_vdev: number of vdev currently handled by rproc
> >>> * @elf_class: firmware ELF class
> >>> @@ -562,6 +563,7 @@ struct rproc {
> >>> size_t table_sz;
> >>> bool has_iommu;
> >>> bool auto_boot;
> >>> + bool sysfs_read_only;
> >>> struct list_head dump_segments;
> >>> int nb_vdev;
> >>> u8 elf_class;
> >>>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-04 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 8:12 [PATCH v5 0/2] remoteproc sysfs fixes/improvements Puranjay Mohan
2022-02-16 8:12 ` [PATCH v5 1/2] remoteproc: Introduce sysfs_read_only flag Puranjay Mohan
2022-02-16 20:04 ` Bjorn Andersson
2022-02-17 6:14 ` Puranjay Mohan
2022-02-18 5:00 ` Kishon Vijay Abraham I
2022-02-18 5:54 ` Bjorn Andersson
2022-03-03 8:00 ` [EXTERNAL] " Puranjay Mohan
2022-03-04 16:53 ` Mathieu Poirier [this message]
2022-02-16 8:12 ` [PATCH v5 2/2] remoteproc: wkup_m3: Set " Puranjay Mohan
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=20220304165346.GA1646337@p14s \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=p-mohan@ti.com \
--cc=vigneshr@ti.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).