linux-kernel - Re: [linux-usb-devel] [PATCH] base/class.c: prevent ooops due to insert/remove race (v3)

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: <Pine.LNX.4.44L0.0711291700260.5666-100000@iolanthe.rowland.org>
Date:	Thu, 29 Nov 2007 17:07:58 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Mark Lord <lkml@....ca>
cc:	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...l.org>,
	<linux-usb-devel@...ts.sourceforge.net>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] [PATCH] base/class.c: prevent ooops due to
 insert/remove race (v3)

On Thu, 29 Nov 2007, Mark Lord wrote:

> > So again, the problem is in the higher up scsi layer, and that is where
> > the problem should already be fixed.
> ..
> 
> Ahhh.. so you figure the Oops should also have been fixed
> as part of the 2.6.24 SCSI fixes ?  That's what I was missing here.

Yes indeed.  I wish I could point you to the exact patch containing the 
fix, but the git software seems to have lost track of it (it's combined
in with a large number of other patches with no obvious way to separate 
it out).  It's also available in the various mailing list archives, but 
I don't have a pointer to it and there's no reasonable way to search 
for it.

The patch in question was written by Matthew Wilcox; it added code to 
the SCSI async-scanning routines to utilize the scan_mutex.  IMO it 
should have been applied to 2.6.23 but it wasn't.

Alan Stern

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