linux-kernel - Re: [PATCH] regmap-irq: Fix bug in regmap_irq_get_irq_reg

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: <165710262393.218789.1320369501599674730.b4-ty@kernel.org>
Date:   Wed, 06 Jul 2022 11:17:03 +0100
From:   Mark Brown <broonie@...nel.org>
To:     aidanmacdonald.0x0@...il.com
Cc:     rafael@...nel.org, m.szyprowski@...sung.com,
        linux-samsung-soc@...r.kernel.org, andy.shevchenko@...il.com,
        gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap-irq: Fix bug in regmap_irq_get_irq_reg_linear()

On Mon, 4 Jul 2022 12:28:47 +0100, Aidan MacDonald wrote:
> irq_reg_stride in struct regmap_irq_chip is often 0, but that
> actually means to use the default stride of 1. The effective
> stride is stored in struct regmap_irq_chip_data->irq_reg_stride
> and will get the corrected default value.
> 
> The default ->get_irq_reg() callback was using the stride from
> the chip definition, which is wrong; fix it to use the effective
> stride from the chip data instead.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap-irq: Fix bug in regmap_irq_get_irq_reg_linear()
      commit: 773d09b4c3acafd35f8b6e90848a39cedc03c52b

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