mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Zongmin Zhou <min_halo@163.com>
Cc: linux-riscv@lists.infradead.org, gregkh@linuxfoundation.org,
	jirislaby@kernel.org, pjw@kernel.org, samuel.holland@sifive.com,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	zhouzongmin@kylinos.cn
Subject: Re: [PATCH] serial: sifive: fix off-by-one in console port bounds check
Date: Sun, 01 Nov 2026 22:16:22 +0000	[thread overview]
Message-ID: <179357138279.2624073.12379269503301547375.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260827014524.19375-1-min_halo@163.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Greg Kroah-Hartman <gregkh@linuxfoundation.org>:

On Thu, 27 Aug 2026 09:45:24 +0800 you wrote:
> From: Zongmin Zhou <zhouzongmin@kylinos.cn>
> 
> sifive_serial_console_ports[] is sized SIFIVE_SERIAL_MAX_PORTS (8), so
> valid indices are 0..7. The bounds check in sifive_serial_probe() uses
> "id > SIFIVE_SERIAL_MAX_PORTS", which lets id == 8 pass and causes an
> out-of-bounds write in __ssp_add_console_port() through
> sifive_serial_console_ports[ssp->port.line].
> 
> [...]

Here is the summary with links:
  - serial: sifive: fix off-by-one in console port bounds check
    https://git.kernel.org/riscv/c/bf961847813d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-11-01 22:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  1:45 Zongmin Zhou
2026-11-01 22:16 ` patchwork-bot+linux-riscv [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=179357138279.2624073.12379269503301547375.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=min_halo@163.com \
    --cc=pjw@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=zhouzongmin@kylinos.cn \
    /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

all inboxes | Powered by JetHome®