linux-ext4 - Re: Crash after umount'ing a disconnected disk (Re: extfs reliability)

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: <4C5B1137.1070001@vlnb.net>
Date:	Thu, 05 Aug 2010 23:29:59 +0400
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	Ted Ts'o <tytso@....edu>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Crash after umount'ing a disconnected disk (Re: extfs reliability)

Ted Ts'o, on 08/04/2010 10:03 PM wrote:
> Ping?
>
> Have you had a chance to check out whether this patch solves the
> problem you were complaining with respect to yanking out the last
> iSCSI or FC link to a hard drive, and then umounting the disk
> afterwards?

Looks like it works. I was able to reach that branch (see AAA in the 
attached log) and it was handled well.

I've also got other (see the attached log file):

1. A bunch of detected hung tasks with call traces.

2. "JBD: recovery failed" I reported before.

The log is basically self talking. I did 2 runs.

Thanks,
Vlad

Download attachment "messages.bz2" of type "application/x-bzip" (18043 bytes)