linux-kernel - Re: [patch 25/45] SCSI: sg: fix races during 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: <1238544620.5000.5.camel@mulgrave.int.hansenpartnership.com>
Date:	Wed, 01 Apr 2009 00:10:20 +0000
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Chris Wright <chrisw@...s-sol.org>, linux-kernel@...r.kernel.org,
	stable@...nel.org, Justin Forbes <jmforbes@...uxtx.org>,
	Zwane Mwaikambo <zwane@....linux.org.uk>,
	Theodore Ts'o <tytso@....edu>,
	Randy Dunlap <rdunlap@...otime.net>,
	Dave Jones <davej@...hat.com>,
	Chuck Wolber <chuckw@...ntumlinux.com>,
	Chris Wedgwood <reviews@...cw.f00f.org>,
	Michael Krufky <mkrufky@...uxtv.org>,
	Chuck Ebbert <cebbert@...hat.com>,
	Domenico Andreoli <cavokz@...il.com>, Willy Tarreau <w@....eu>,
	Rodrigo Rubira Branco <rbranco@...checkpoint.com>,
	Jake Edge <jake@....net>, Eugene Teo <eteo@...hat.com>,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
	Tony Battersby <tonyb@...ernetics.com>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	Douglas Gilbert <dgilbert@...erlog.com>
Subject: Re: [patch 25/45] SCSI: sg: fix races during device removal

On Tue, 2009-03-31 at 16:31 -0700, Linus Torvalds wrote: 
> 
> On Tue, 31 Mar 2009, Chris Wright wrote:
> > 
> > From: Tony Battersby <tonyb@...ernetics.com>
> > 
> > upstream commit: c6517b7942fad663cc1cf3235cbe4207cf769332
> > 
> > sg has the following problems related to device removal:
> 
> Hmm. Is this a new problem to 2.6.29?

No, it's fairly old

> The patch is pretty big (certainly _way_ over the official -stable limit), 
> and I don't know how critical or new this bug was. I doubt it has gotten 
> much testing in the development branch either, yet.

Well, I considered the patch too high risk for -rc, so we elected to put
it into the development branch with the understanding that we'd backport
it to 2.6.29 provided it proved stable.

The races it fixes are hard to trigger.  However, we do have an oops
report on it:

http://marc.info/?l=linux-kernel&m=123316111415677

or at least which is fixed by the three patch series.

> So please convince me that this shouldn't wait a bit, or at least point me 
> to the problem reports to convince me that the size limit should be 
> ignored.

I think we could wait a bit to see if any issues turn up in 2.6.30
testing.  I think it should go in eventually, though.

James


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