linux-kernel - Re: [PATCH] spi: orion: set devdata properly as it is being used later

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: <161798356987.48466.7574385472200837460.b4-ty@kernel.org>
Date:   Fri,  9 Apr 2021 17:22:39 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Muhammad Usama Anjum <musamaanjum@...il.com>,
        open list <linux-kernel@...r.kernel.org>,
        Tian Tao <tiantao6@...ilicon.com>,
        "open list:SPI SUBSYSTEM" <linux-spi@...r.kernel.org>
Cc:     Mark Brown <broonie@...nel.org>, kernel-janitors@...r.kernel.org,
        colin.king@...onical.com, dan.carpenter@...cle.com
Subject: Re: [PATCH] spi: orion: set devdata properly as it is being used later

On Fri, 9 Apr 2021 00:57:18 +0500, Muhammad Usama Anjum wrote:
> If device_get_match_data returns NULL, devdata isn't being updated
> properly. It is being used later in the function. Both devdata and
> spi->devdata should be updated to avoid NULL pointer dereference.

Applied to

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

Thanks!

[1/1] spi: orion: set devdata properly as it is being used later
      commit: e980048263ba72dcdbbf45d59e84c02001340f75

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