linux-kernel - Re: Linux 3.0 oopses when pulling a USB CDROM

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: <20110703181615.GC15637@one.firstfloor.org>
Date:	Sun, 3 Jul 2011 20:16:15 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Dan Williams <dan.j.williams@...il.com>
Cc:	Alan Stern <stern@...land.harvard.edu>, axboe@...nel.dk,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	Andi Kleen <andi@...stfloor.org>,
	Dave Jones <davej@...hat.com>,
	SCSI development list <linux-scsi@...r.kernel.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re: Linux 3.0 oopses when pulling a USB CDROM

> Not sure it's related, but it sounds like the hotplug failures being
> seen with libsas hotplug.  Have not had a chance yet to track it down
> further with isci, but mvsas developer Xiangliang Yu is reporting:

It looks somewhat different: he has a bad pointer, not a NULL pointer,
and it's in elv_completed_request() (but that may be related to 
the different request types)

> 
> http://marc.info/?l=linux-scsi&m=130707166512002&w=2
> 
> He tracked it down to a suspected regression between .39-rc4 and
> .39-rc5 but did not finalize the bisect.

I can check if it disappears with .39-rc4.

> The isci driver sees this and other signatures all seemingly related
> to early device tear down and only when pulling a drive with in-flight
> i/o.

In my case it's not really in flight IO, but umount after pull with an
idle drive.

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