linux-kernel - Re: [PATCH RT 2/4] acpi/rt: Convert acpi_gbl_hardware lock back to a raw_spinlock

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]

Date:	Fri, 14 Jun 2013 17:41:01 +0200
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	linux-kernel@...r.kernel.org,
	linux-rt-users <linux-rt-users@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Carsten Emde <C.Emde@...dl.org>,
	John Kacur <jkacur@...hat.com>,
	Clark Williams <clark@...hat.com>, stable-rt@...r.kernel.org
Subject: Re: [PATCH RT 2/4] acpi/rt: Convert acpi_gbl_hardware lock back to
 a raw_spinlock_t

On 06/14/2013 05:16 PM, Steven Rostedt wrote:
> Hi Sebastian,

Hi Steven,

> 
> Any reason that this patch was dropped for 3.8? We hit this exact same
> bug recently with a 3.8-rt kernel.

No particular reason. Going through my log of the queue I have to say
that it was never in the queue starting v3.8.

The only ACPI patches that were dropped are:

 # ACPI
 # Dropped those two as they cause a scheduling in atomic failure and
 # we have no clue why we made those locks raw in the first place.
 # acpi-make-gbl-hardware-lock-raw.patch
 # acpi-make-ec-lock-raw-as-well.patch

 # This one is just a follow up to the raw spin locks
 # Simple raw spinlock based waitqueue
 # wait-simple-version.patch
 # acpi-gpe-use-wait-simple.patch

but that wasn't me.

In that case I try to bring it back in.

> -- Steve

Sebastian
--
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/