linux-kernel - Re: [PATCH 06/19] gpio: ath79: make use of raw

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: <20170313205130.2b5c5272@tock>
Date:   Mon, 13 Mar 2017 20:51:30 +0100
From:   Alban <albeu@...e.fr>
To:     Julia Cartwright <julia@...com>
Cc:     Aban Bedel <albeu@...e.fr>,
        Linus Walleij <linus.walleij@...aro.org>,
        Alexandre Courbot <gnurou@...il.com>,
        <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 06/19] gpio: ath79: make use of raw_spinlock variants

On Thu, 9 Mar 2017 10:21:53 -0600
Julia Cartwright <julia@...com> wrote:

> The ath79 gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel.  Because the spinlock_t type becomes a "sleeping"
> spinlock w/ RT kernels, it is not suitable to be used with irq_chips.
> 
> A quick audit of the operations under the lock reveal that they do only
> minimal, bounded work, and are therefore safe to do under a raw spinlock.
> 
> Signed-off-by: Julia Cartwright <julia@...com>

Acked-by: Aban Bedel <albeu@...e.fr>

Content of type "application/pgp-signature" skipped