All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 196223] jdb2 journal - hung after suspend-resume test
Date: Fri, 30 Jun 2017 14:55:10 +0000	[thread overview]
Message-ID: <bug-196223-13602-nu5BpJxQvt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196223-13602@https.bugzilla.kernel.org/>

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

Theodore Tso (tytso@mit.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@mit.edu

--- Comment #3 from Theodore Tso (tytso@mit.edu) ---
Since this commit has been implicated in another problem (with quite different
symptoms) it's a bit of a long shot, but since you have a quick and easy
reproduction, can you try reverting 81378da64de6: "jbd2: mark the transaction
context with the scope GFP_NOFS context" and see if that makes the hang go
away?

Failing that, I might have to ask you to do a bisect on the ext4 patches added
during the 4.12 merge window.

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

  parent reply	other threads:[~2017-06-30 14:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  6:11 [Bug 196223] New: jdb2 journal - hung after suspend-resume test bugzilla-daemon
2017-06-30  7:41 ` [Bug 196223] " bugzilla-daemon
2017-06-30  7:51 ` bugzilla-daemon
2017-06-30 14:55 ` bugzilla-daemon [this message]
2017-07-03  6:15 ` bugzilla-daemon
2017-07-03 13:49 ` bugzilla-daemon
2017-07-04  5:56 ` bugzilla-daemon
2017-07-04 22:49 ` bugzilla-daemon
2017-07-05 13:12 ` bugzilla-daemon
2017-07-07  8:20 ` bugzilla-daemon
2017-07-07 14:14 ` bugzilla-daemon
2017-07-08 18:58 ` bugzilla-daemon
2017-07-08 19:22 ` bugzilla-daemon
2017-07-09  5:05 ` bugzilla-daemon
2017-07-09  5:27 ` bugzilla-daemon
2017-07-10  5:04 ` bugzilla-daemon
2017-07-10  5:10 ` bugzilla-daemon
2017-07-10  5:14 ` bugzilla-daemon
2017-07-10 12:58 ` bugzilla-daemon
2017-07-10 22:52 ` bugzilla-daemon
2017-07-11  8:12 ` bugzilla-daemon
2017-07-11  8:40 ` bugzilla-daemon
2017-07-11  9:59 ` bugzilla-daemon
2017-07-11 13:15 ` bugzilla-daemon
2017-07-11 17:17 ` bugzilla-daemon
2017-07-12  7:52 ` bugzilla-daemon
2017-07-12 14:17 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-196223-13602-nu5BpJxQvt@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.