linux-ext4 - [Bug 42763] New: directory access hangs without error

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-next>] [day] [month] [year] [list]

Date:	Mon, 13 Feb 2012 03:41:28 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 42763] New: directory access hangs without error

https://bugzilla.kernel.org/show_bug.cgi?id=42763

           Summary: directory access hangs without error
           Product: File System
           Version: 2.5
    Kernel Version: 3.2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@...nel-bugs.osdl.org
        ReportedBy: ebuddington@...leyan.edu
        Regression: No

Kernel 3.2.5
ext4 over RAID-6

I have a specific directory that freezes all processes that try to getdents()
or open() a new file. In some cases, the kernel gives  me "blocked for more
than 120 seconds" messages, often reporting that the process is stuck in
ext4_getblk.

I have found no errors, however. The stuck processes stay stuck forever (at
least hours), and dmesg shows no complaints about RAID, filesystem, or anything
else. Full reads of the RAID devices work without hanging, and drive self-tests
pass.

Other processes are able to access other parts of the filesystem normally; this
is not a system-wide or fs-wide hang.

Rebooting and fscking made the directory accessible again, but now there is a
different directory exhibiting the problem (unknown whether it had the problem
before the fsck/reboot)

This particular problem exhibited itself for the first time after tests of my
multi-threaded 'du' that beat the filesystem with a few dozen threads
simultaneously.

Given that this seems to very reproducible, I have many opportunities to poke
at a hung process, query the filesystem, or recompile the kernel in any way
that would be helpful; I just don't know to approach it from here.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
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