linux-ext4 - Re: Oops in block/ext4 layer on USB3 hard drive connect

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]

Message-ID: <20111004162231.GA5155@xanatos>
Date:	Tue, 4 Oct 2011 09:22:31 -0700
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	Lukas Czerner <lczerner@...hat.com>
Cc:	Jens Axboe <axboe@...nel.dk>, Theodore Ts'o <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	linux-ext4@...r.kernel.org,
	USB Storage List <usb-storage@...ts.one-eyed-alien.net>
Subject: Re: Oops in block/ext4 layer on USB3 hard drive connect

On Tue, Oct 04, 2011 at 08:52:23AM +0200, Lukas Czerner wrote:
> On Mon, 3 Oct 2011, Sarah Sharp wrote:
> 
> > Hi Jens, Ted, and Andreas,
> > 
> > A co-worker of mine found a 100% reproducible oops that happens when a
> > IOMEGA USB 3.0 hard drive is plugged into a particular machine.  It
> > looks like an oops in the block or EXT4 layer, and it doesn't seem to be
> > in the xHCI (USB 3.0 host controller) driver.  (Although looking at the
> > log again, it seems show a cut-off oops at the beginning of the log...)
> > 
> > This appears on the 3.0.4 stable kernel.  dmesg is attached.  Let me
> > know if you need any other info to help solve this issue.
> > 
> > Sarah Sharp
> > 
> 
> Hello,
> 
> looking at the dmesg it really looks like there is a trace missing,
> could you post the full oops ?

I asked the tech person for the beginning of the oops message, but I
haven't heard back from them yet.

Sarah Sharp
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html