Messages in this thread | | | Subject | Re: [PATCH 2/2] ARM: zynq: Use memcpy_toio instead of memcpy on smp bring-up | From | Michal Simek <> | Date | Thu, 8 Aug 2019 11:19:46 +0200 |
| |
On 06. 08. 19 14:49, Luis Araneda wrote: > Hi Michal, > > On Tue, Aug 6, 2019 at 2:42 AM Michal Simek <michal.simek@xilinx.com> wrote: >> On 06. 08. 19 5:07, Luis Araneda wrote: >>> This fixes a kernel panic (read overflow) on memcpy when >>> FORTIFY_SOURCE is enabled. >>> >>> The computed size of memcpy args are: >>> - p_size (dst): 4294967295 = (size_t) -1 >>> - q_size (src): 1 >>> - size (len): 8 >>> >>> Additionally, the memory is marked as __iomem, so one of >>> the memcpy_* functions should be used for read/write >>> >>> Signed-off-by: Luis Araneda <luaraneda@gmail.com> > [...] >> I would consider this one as stable material. Please also add there link >> to the patch which this patch fixes. > > I'm dropping stable CC (for now), as I'm not sure I completely > understood the process for inclusion in stable trees. > Do I have to wait for the patch to be on Linus' tree before CCing stable?
just put Cc: to commit message and they will pick it up.
> > As for the link which this patch fixes, you mean > aa7eb2bb4e4a22e41bbe4612ff46e5885b13c33e (arm: zynq: Add smp support)? > where you added SMP support for zynq.
yes but make sha1 only 12char long.
M
-- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
[unhandled content-type:application/pgp-signature] | |