linux-ext4 - Re: jbd2 task hung in jbd2_journal_commit

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: <YFTAZdfbKUsMmb9A@mit.edu>
Date:   Fri, 19 Mar 2021 11:16:53 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     Shashidhar Patil <shashidhar.patil@...il.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: jbd2 task hung in jbd2_journal_commit_transaction

On Thu, Mar 18, 2021 at 12:27:44PM +0530, Shashidhar Patil wrote:
> Hi Theodore,
>     I forgot to include two important  details , the stack trace of
> loop0 driver and sar output, which clearly nail  the problem.
> The losetup with Ubuntu16.05 does not have O_DIRECT support  and we
> were not aware of bypassing of journalling if
> O_DIRECT combined with preallocated file scenario.

Which version of the kernel are you using?  The use of O_DIRECT for
loop devices requires kernel and losetup support.  (Also note that
upstream developers really generally don't pay attention --- or
support --- distribution kernels unless they work for the company for
which you are paying $$$ for support, and Ubuntu 16.05 isn't even a
Long-Term Support distribution.)

My suggestion is to see if you can replicate the problem on a modern
userspace with the latest kernel.  And if not, then that's an object
lesson about why using a antediluvian is not a great life choice.  :-)

Cheers,

						- Ted