Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1631503
| From | Tony Lindgren <tony@atomide.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] misc: sram-exec: Use aligned fncpy instead of memcpy |
| Date | 2017-04-26 17:00 +0200 |
| Message-ID | <tAwA9-3Ev-7@gated-at.bofh.it> (permalink) |
| References | <tuIXn-21C-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
* Dave Gerlach <d-gerlach@ti.com> [170410 07:55]:
> Currently the sram-exec functionality, which allows allocation of
> executable memory and provides an API to move code to it, is only
> selected in configs for the ARM architecture. Based on commit
> 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol manipulation macros for
> function body copying") simply copying a C function pointer address
> using memcpy without consideration of alignment and Thumb is unsafe on
> ARM platforms.
>
> The aforementioned patch introduces the fncpy macro which is a safe way
> to copy executable code on ARM platforms, so let's make use of that here
> rather than the unsafe plain memcpy that was previously used by
> sram_exec_copy. Now sram_exec_copy will move the code to "dst" and
> return an address that is guaranteed to be safely callable.
>
> In the future, architectures hoping to make use of the sram-exec
> functionality must define an fncpy macro just as ARM has done to
> guarantee or check for safe copying to executable memory before allowing
> the arch to select CONFIG_SRAM_EXEC.
Looks good to me:
Acked-by: Tony Lindgren <tony@atomide.com>
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH v2] misc: sram-exec: Use aligned fncpy instead of memcpy Tony Lindgren <tony@atomide.com> - 2017-04-26 17:00 +0200
csiph-web