From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Ayush Singh <ayush@beagleboard.org>
Cc: xypron.glpk@gmx.de, Jason Kridner <jkridner@beagleboard.org>,
Deepak Khatri <lorforlinux@beagleboard.org>,
d-gole@ti.com, Robert Nelson <robertcnelson@beagleboard.org>,
Andrew Davis <afd@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Gibson <david@gibson.dropbear.id.au>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Pantelis Antoniou <pantelis.antoniou@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [Question] Status of user-space dynamic overlays API
Date: Mon, 24 Feb 2025 09:37:56 +0100 [thread overview]
Message-ID: <CAMuHMdUhw6q1DAOBJwG5FJUs_QHj3hZMD3damOo2uLZQgS9e7A@mail.gmail.com> (raw)
In-Reply-To: <9c326bb7-e09a-4c21-944f-006b3fad1870@beagleboard.org>
Hi Ayush,
On Sat, 22 Feb 2025 at 21:14, Ayush Singh <ayush@beagleboard.org> wrote:
> # Challenges
>
> ## Security
>
> The concerns regarding security seemed to show up in the other
> proposals. There was a proposal to have a devicetree property to
> allow/deny the application of overlays in some nodes, with default being
> deny. Was it insufficient?
This is the most important issue: using DT overlays, you can change
about anything. There is no protection yet to limit this to e.g. the
expansion connectors on your board.
This is what the various WIP "connector" abstractions are trying
to solve.
> ## Memory Leaks
>
> Currently, updating/removing properties leaks memory. Was it one of the
> reasons for the rejection of previous proposals?
IMO this is a minor issue. I am sure this can be improved upon. We just
need some way to keep track of which properties are part of the initial
FDT (and thus can't be freed), and which were allocated dynamically.
> [0]:
> https://lore.kernel.org/all/1417605808-23327-1-git-send-email-pantelis.antoniou@konsulko.com/#t
FTR, I do keep this up to date:
https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git/log/?h=topic/overlays
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2025-02-24 8:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 20:13 [Question] Status of user-space dynamic overlays API Ayush Singh
2025-02-22 20:31 ` Heinrich Schuchardt
2025-02-24 5:58 ` Ayush Singh
2025-02-24 8:37 ` Geert Uytterhoeven [this message]
2025-02-24 10:09 ` Ayush Singh
2025-02-24 13:29 ` Herve Codina
2025-03-05 4:31 ` David Gibson
2025-03-10 5:22 ` Ayush Singh
2025-03-05 4:27 ` David Gibson
2025-02-24 11:24 ` Luca Ceresoli
2025-04-30 10:18 ` Ayush Singh
2025-04-30 13:07 ` Luca Ceresoli
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=CAMuHMdUhw6q1DAOBJwG5FJUs_QHj3hZMD3damOo2uLZQgS9e7A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=afd@ti.com \
--cc=ayush@beagleboard.org \
--cc=d-gole@ti.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jkridner@beagleboard.org \
--cc=lorforlinux@beagleboard.org \
--cc=luca.ceresoli@bootlin.com \
--cc=pantelis.antoniou@gmail.com \
--cc=robertcnelson@beagleboard.org \
--cc=xypron.glpk@gmx.de \
/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).