linux-kernel - Re: 2.6.32-rc5: surprise removal of USB mass storage, and whole system goes to hell

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]

Date:	Wed, 28 Oct 2009 15:07:31 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Pavel Machek <pavel@....cz>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.32-rc5: surprise removal of USB mass storage, and whole
	system goes to hell

On Wed, Oct 28 2009, Jens Axboe wrote:
> On Wed, Oct 28 2009, Jiri Kosina wrote:
> > On Tue, 27 Oct 2009, Pavel Machek wrote:
> > 
> > > I did remove one harddrive w/o unmounting, and now the whole system
> > > becomes unusable :-(: (whole dmesg attached).
> > > 
> > > Stuff like "sync" hangs, and I'll probably have to reboot soon.
> > 
> > From the traces it seems that it might be related to the new per-bdi 
> > writeback stuff ... adding Jens to CC.
> 
> It looks like the IO isn't being errored on the device side, or perhaps
> it just got stuck. Pavel, if you can reproduce, please try with this
> tracing patch. Apply it, and then do something ala:
> 
> # cd /sys/kernel/debug/tracing
> # echo 0 events/enable
> # echo 1 events/writeback/enable
> # echo 0 > trace
> 
> then start the act of reproducing, and finally
> 
> # cat trace > /tmp/foo
> 
> and send the output of foo here. Thanks!

I can reproduce this. The writeback work gets queued, we notice the task
isn't there and wake up the default task. And then nothing happens, I
wonder if the bdi is gone.

I'll fiddle around with this.

-- 
Jens Axboe

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