linux-ext4 - [Bug 71791] Unlinking a file that was moved to another folder but still open by other process blocks either process (not always reproducible)

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:	Sun, 16 Mar 2014 07:20:29 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 71791] Unlinking a file that was moved to another folder but
 still open by other process blocks either process (not always reproducible)

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

Zheng Liu <gnehzuil.liu@...il.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gnehzuil.liu@...il.com

--- Comment #2 from Zheng Liu <gnehzuil.liu@...il.com> ---
I guess that the journal mode is 'data=ordered', right?  Could you please try
to switch the journal mode to 'data=writeback' and look at whether or not the
problem can be reproduced?

In our product system, we met a hang which is caused by 'data=ordered' under a
heavy IO workload.  When the user uses 'rm' command to delete a file,
ext4_begin_ordered_truncate() should be called with 'data=ordered' and it could
trigger write back kernel thread to write out the dirty data.  Then
truncate_inode_pages() will wait on write back.

Regards,
                                                - Zheng

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