From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, robh@kernel.org,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Linux-imx@nxp.com
Subject: Re: [PATCH] Input: keyboard - imx_sc: Correct SCU message structure to avoid stack corruption
Date: Fri, 15 Nov 2019 11:34:35 -0800 [thread overview]
Message-ID: <20191115193435.GV13374@dtor-ws> (raw)
In-Reply-To: <1573730499-2224-1-git-send-email-Anson.Huang@nxp.com>
On Thu, Nov 14, 2019 at 07:21:39PM +0800, Anson Huang wrote:
> The SCU message's data field used for receiving response data
> from SCU should be 32-bit width, as SCU will send back 32-bit
> width data, correct it to avoid kernel panic of stack protection
> when CONFIG_CC_HAVE_STACKPROTECTOR_SYSREG is enabled.
>
> [ 1.950768] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted
> [ 1.980607] Workqueue: events imx_sc_check_for_events
> [ 1.985657] Call trace:
> [ 1.988104] dump_backtrace+0x0/0x140
> [ 1.991768] show_stack+0x14/0x20
> [ 1.995090] dump_stack+0xb4/0xf8
> [ 1.998407] panic+0x158/0x324
> [ 2.001463] print_tainted+0x0/0xa8
> [ 2.004950] imx_sc_check_for_events+0x18c/0x190
> [ 2.009569] process_one_work+0x198/0x320
> [ 2.013579] worker_thread+0x48/0x420
> [ 2.017252] kthread+0xf0/0x120
> [ 2.020394] ret_from_fork+0x10/0x18
> [ 2.023977] SMP: stopping secondary CPUs
> [ 2.027901] Kernel Offset: disabled
> [ 2.031391] CPU features: 0x0002,2100600c
> [ 2.035401] Memory Limit: none
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
Applied, thank you.
> ---
> drivers/input/keyboard/imx_sc_key.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/imx_sc_key.c b/drivers/input/keyboard/imx_sc_key.c
> index dd57daa..5379952 100644
> --- a/drivers/input/keyboard/imx_sc_key.c
> +++ b/drivers/input/keyboard/imx_sc_key.c
> @@ -35,7 +35,7 @@ struct imx_key_drv_data {
>
> struct imx_sc_msg_key {
> struct imx_sc_rpc_msg hdr;
> - u8 state;
> + u32 state;
> };
>
> static int imx_sc_key_notify(struct notifier_block *nb,
> --
> 2.7.4
>
--
Dmitry
prev parent reply other threads:[~2019-11-15 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 11:21 [PATCH] Input: keyboard - imx_sc: Correct SCU message structure to avoid stack corruption Anson Huang
2019-11-15 19:34 ` Dmitry Torokhov [this message]
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=20191115193435.GV13374@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Anson.Huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox