linux-kernel - Re: [patch]hp_accel: Fix race in device removal

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: <20100510154632.bbe181d8.akpm@linux-foundation.org>
Date:	Mon, 10 May 2010 15:46:32 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Oliver Neukum <oneukum@...e.de>
Cc:	Eric Piel <eric.piel@...mplin-utc.net>,
	Pavel Machek <pavel@....cz>,
	Pavel Herrmann <morpheus.ibis@...il.com>,
	lm-sensors@...sensors.org, linux-kernel@...r.kernel.org,
	stable@...nel.org
Subject: Re: [patch]hp_accel: Fix race in device removal

On Fri, 7 May 2010 18:04:20 +0200
Oliver Neukum <oneukum@...e.de> wrote:

> >From 505056649f5ecb1ebb086981243b9870ce961a87 Mon Sep 17 00:00:00 2001
> From: Oliver Neukum <oliver@...kum.org>
> Date: Fri, 7 May 2010 18:02:07 +0200
> Subject: [PATCH] hp_accel: Fix race in device removal
> 
> The work queue has to be flushed after the device has been made
> inaccessible.
> 

You cc'ed stable@...nel.org so presumably you think it's a pretty
serious bug.

But alas, I (and presumably others) cannot confirm that, because you
didn't describe the bug :( This also means that if someone hits a
problem with this driver, they won't easily be able to work out whether
this patch will fix it.


Under what circumstances does it trigger?

What are the observed effects when it triggers?

Please always include this sort of information when sending bugfixes, thanks.
--
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/