linux-kernel - Re: [PATCH] spi: mediatek: Avoid NULL pointer crash in interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <164364718000.1030778.7318932635935946052.b4-ty@kernel.org>
Date:   Mon, 31 Jan 2022 16:39:40 +0000
From:   Mark Brown <broonie@...nel.org>
To:     matthias.bgg@...il.com,
        Benjamin Gaignard <benjamin.gaignard@...labora.com>
Cc:     linux-mediatek@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, kernel@...labora.com,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: mediatek: Avoid NULL pointer crash in interrupt

On Mon, 31 Jan 2022 15:17:08 +0100, Benjamin Gaignard wrote:
> In some case, like after a transfer timeout, master->cur_msg pointer
> is NULL which led to a kernel crash when trying to use master->cur_msg->spi.
> mtk_spi_can_dma(), pointed by master->can_dma, doesn't use this parameter
> avoid the problem by setting NULL as second parameter.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-linus

Thanks!

[1/1] spi: mediatek: Avoid NULL pointer crash in interrupt
      commit: f83a96e5f033fbbd21764705cb9c04234b96218e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark