linux-kernel - Re: [PATCH v2 1/2] regmap: fix page selection for noinc reads

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: <160072444712.56996.10601329042842573406.b4-ty@kernel.org>
Date:   Mon, 21 Sep 2020 22:40:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     "Rafael J. Wysocki" <rafael@...nel.org>,
        Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Ben Whitten <ben.whitten@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] regmap: fix page selection for noinc reads

On Thu, 17 Sep 2020 18:34:04 +0300, Dmitry Baryshkov wrote:
> Non-incrementing reads can fail if register + length crosses page
> border. However for non-incrementing reads we should not check for page
> border crossing. Fix this by passing additional flag to _regmap_raw_read
> and passing length to _regmap_select_page basing on the flag.

Applied to

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

Thanks!

[1/2] regmap: fix page selection for noinc reads
      commit: 4003324856311faebb46cbd56a1616bd3f3b67c2
[2/2] regmap: fix page selection for noinc writes
      commit: 05669b63170771d554854c0e465b76dc98fc7c84

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