linux-kernel - Re: [PATCH] regmap: debugfs: Don't sleep while atomic for fast

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: <159494387342.42385.3653769837072833103.b4-ty@kernel.org>
Date:   Fri, 17 Jul 2020 00:57:58 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Douglas Anderson <dianders@...omium.org>
Cc:     Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Rohit Kumar <rohitkr@...eaurora.org>
Subject: Re: [PATCH] regmap: debugfs: Don't sleep while atomic for fast_io regmaps

On Wed, 15 Jul 2020 16:46:15 -0700, Douglas Anderson wrote:
> If a regmap has "fast_io" set then its lock function uses a spinlock.
> That doesn't work so well with the functions:
> * regmap_cache_only_write_file()
> * regmap_cache_bypass_write_file()
> 
> Both of the above functions have the pattern:
> 1. Lock the regmap.
> 2. Call:
>    debugfs_write_file_bool()
>      copy_from_user()
>        __might_fault()
>          __might_sleep()
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: debugfs: Don't sleep while atomic for fast_io regmaps
      commit: 299632e54b2e692d2830af84be51172480dc1e26

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