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

--- Comment #2 from zhenbianshu@foxmail.com ---

(In reply to Theodore Tso from comment #1)

It shouldn't be the case that the journal's data=ordered writeback would be
taking the i_data semaphore for writing.   

I'm guessing what is happening is that journal is causing a lot of I/O
operations because of data=ordered mode (e.g., not data=writeback), and this
is delaying a read which a writeback thread was trying to do while it was
holding a write lock on the inode's semaphore.

can you please show me the related source code of writeback holding a write
lock?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.