All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Luis Araneda <luaraneda@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
	stable@vger.kernel.org, michal.simek@xilinx.com
Subject: Re: [PATCH 2/2] ARM: zynq: Use memcpy_toio instead of memcpy on smp bring-up
Date: Tue, 6 Aug 2019 07:17:17 +0200	[thread overview]
Message-ID: <20190806051717.GC8525@kroah.com> (raw)
In-Reply-To: <20190806030718.29048-3-luaraneda@gmail.com>

On Mon, Aug 05, 2019 at 11:07:18PM -0400, 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>
> ---
>  arch/arm/mach-zynq/platsmp.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Luis Araneda <luaraneda@gmail.com>
Cc: linux@armlinux.org.uk, michal.simek@xilinx.com,
	stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: zynq: Use memcpy_toio instead of memcpy on smp bring-up
Date: Tue, 6 Aug 2019 07:17:17 +0200	[thread overview]
Message-ID: <20190806051717.GC8525@kroah.com> (raw)
In-Reply-To: <20190806030718.29048-3-luaraneda@gmail.com>

On Mon, Aug 05, 2019 at 11:07:18PM -0400, 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>
> ---
>  arch/arm/mach-zynq/platsmp.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  reply	other threads:[~2019-08-06  5:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  3:07 [PATCH 0/2] ARM: zynq: smp improvements Luis Araneda
2019-08-06  3:07 ` Luis Araneda
2019-08-06  3:07 ` [PATCH 1/2] ARM: zynq: support smp in thumb mode Luis Araneda
2019-08-06  3:07   ` Luis Araneda
2019-08-06  5:17   ` Greg KH
2019-08-06  5:17     ` Greg KH
2019-08-06  6:39   ` Michal Simek
2019-08-06  6:39     ` Michal Simek
2019-08-06 12:40     ` Luis Araneda
2019-08-06 12:40       ` Luis Araneda
2019-08-08  9:18       ` Michal Simek
2019-08-08  9:18         ` Michal Simek
2019-08-06  3:07 ` [PATCH 2/2] ARM: zynq: Use memcpy_toio instead of memcpy on smp bring-up Luis Araneda
2019-08-06  3:07   ` Luis Araneda
2019-08-06  5:17   ` Greg KH [this message]
2019-08-06  5:17     ` Greg KH
2019-08-06  6:41   ` Michal Simek
2019-08-06  6:41     ` Michal Simek
2019-08-06 12:49     ` Luis Araneda
2019-08-06 12:49       ` Luis Araneda
2019-08-08  9:19       ` Michal Simek
2019-08-08  9:19         ` Michal Simek
2019-08-06  5:17 ` [PATCH 0/2] ARM: zynq: smp improvements Greg KH
2019-08-06  5:17   ` Greg KH

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=20190806051717.GC8525@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luaraneda@gmail.com \
    --cc=michal.simek@xilinx.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.