Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Bjørn Mork" <bjorn@mork.no>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>
Cc: "Steven J . Hill" <Steven.Hill@imgtec.com>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols
Date: Sun, 25 Aug 2024 13:50:20 +0100	[thread overview]
Message-ID: <7f0602dc-8a47-46cb-a12f-09afc082b48f@app.fastmail.com> (raw)
In-Reply-To: <20240824144133.1464835-1-bjorn@mork.no>



在2024年8月24日八月 下午3:41,Bjørn Mork写道:
> Boards based on the same SoC family can use different boot loaders.
> These may pass numeric arguments which we erroneously interpret as
> command line or environment pointers. Such errors will cause boot
> to halt at an early stage since commit 056a68cea01e ("mips: allow
> firmware to pass RNG seed to kernel").
>
> One known example of this issue is a HPE switch using a BootWare
> boot loader.  It was found to pass these arguments to the kernel:
>
>   0x00020000 0x00060000 0xfffdffff 0x0000416c
>
> We can avoid hanging by validating that both passed pointers are in
> KSEG1 as expected.

Hi Bjorn,

This is actually breaking 64 bit systems passing fw_args in XKPHYS or KSEG0.

Maybe something like:

static inline bool valid_fw_arg(unsigned long arg)
{
#ifdef CONFIG_64BIT
	if (arg >= XKPHYS && arg < XKSEG)
		return TRUE;
#endif
	return arg >= CKSEG0 && arg < CKSSEG;
}

Will be more robust.

Thanks
- Jiaxun

>
> Cc: stable@vger.kernel.org
> Fixes: 14aecdd41921 ("MIPS: FW: Add environment variable processing.")
> Signed-off-by: Bjørn Mork <bjorn@mork.no>
> ---
>  arch/mips/fw/lib/cmdline.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/fw/lib/cmdline.c b/arch/mips/fw/lib/cmdline.c
> index 892765b742bb..51238c4f9455 100644
> --- a/arch/mips/fw/lib/cmdline.c
> +++ b/arch/mips/fw/lib/cmdline.c
> @@ -22,7 +22,7 @@ void __init fw_init_cmdline(void)
>  	int i;
> 
>  	/* Validate command line parameters. */
> -	if ((fw_arg0 >= CKSEG0) || (fw_arg1 < CKSEG0)) {
> +	if (fw_arg0 >= CKSEG0 || fw_arg1 < CKSEG0 || fw_arg1 >= CKSEG2) {
>  		fw_argc = 0;
>  		_fw_argv = NULL;
>  	} else {
> @@ -31,7 +31,7 @@ void __init fw_init_cmdline(void)
>  	}
> 
>  	/* Validate environment pointer. */
> -	if (fw_arg2 < CKSEG0)
> +	if (fw_arg2 < CKSEG0 || fw_arg2 >= CKSEG2)
>  		_fw_envp = NULL;
>  	else
>  		_fw_envp = (int *)fw_arg2;
> -- 
> 2.39.2

-- 
- Jiaxun

  reply	other threads:[~2024-08-25 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-24 14:41 [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols Bjørn Mork
2024-08-25 12:50 ` Jiaxun Yang [this message]
2024-08-25 13:56   ` Maciej W. Rozycki
2024-08-25 14:44   ` Bjørn Mork
2024-08-25 15:18     ` Maciej W. Rozycki
2024-08-25 15:47       ` Bjørn Mork
2024-08-25 19:59         ` Maciej W. Rozycki
2024-08-26  8:52           ` Bjørn Mork
2024-08-26 13:17     ` Jiaxun Yang
2024-08-28 22:15 ` kernel test robot

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=7f0602dc-8a47-46cb-a12f-09afc082b48f@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=Steven.Hill@imgtec.com \
    --cc=bjorn@mork.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tsbogend@alpha.franken.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