linux-kernel - Re: [PATCH] regmap: Make regmap-mmio usable from atomic contexts

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <519F89D7.3000009@wwwdotorg.org>
Date:	Fri, 24 May 2013 09:40:07 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Lars-Peter Clausen <lars@...afoo.de>
CC:	Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: Make regmap-mmio usable from atomic contexts

On 05/24/2013 02:29 AM, Lars-Peter Clausen wrote:
> regmap-mmio uses a spinlock with spin_lock() and spin_unlock() for locking.
> To be able to use the regmap API from different contexts (atomic vs non-atomic),
> without the risk of race conditions, we need to use spin_lock_irqsave() and
> spin_lock_irqrestore() instead. A new field, the spinlock_flags field, is added
> to regmap struct to store the flags between regmap_{,un}lock_spinlock(). The
> spinlock_flags field itself is also protected by the spinlock.

Reviewed-by: Stephen Warren <swarren@...dia.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/