linux-ext4 - Re: Ext4 stuck at wait_transaction

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]

Message-ID: <20160827190236.aoeaphgniuqzwkay@thunk.org>
Date:   Sat, 27 Aug 2016 15:02:36 -0400
From:   Theodore Ts'o <tytso@....edu>
To:     Roy Yang <roy@...esity.com>
Cc:     linux-ext4@...r.kernel.org
Subject: Re: Ext4 stuck at wait_transaction_locked

On Sat, Aug 27, 2016 at 09:29:51AM -0700, Roy Yang wrote:
> Yes, that is the process which was killed by oom killer since it is
> exceeding 1.4GB memory.
> The full dmesg and also processes stuck at ext4
> start_this_handle/wait_transaction_locked
> are attached.

Yeah, unfortunately it's not helpful.  My guess is that it's somewhere
in the call chain of page fault code calling ext4_page_mkwrite() where
we have a bad error handling path, but finding it will be a pain.

Since you have a reliable repro, would you be willing to try and
reproduce the problem with the latest upstream kernel?  If you can
reproduce it there, I'll promise to help you instrument the kernel so
we can track down the problem.

> I also searched Redhat support portal, online resource. Similar issue
> was found but not sure whether
> upstream patch 2c869b262a10ca99cb866d04087d75311587a30c mentioned at
> https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-checkins/y6n90Mqop7A
> has addressed the problem.

No, this patch fixes a problem with online resize, which has nothing
to do with what you are seeing.

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