linux-ext4.vger.kernel.org archive mirror
 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: Mon, 03 Jul 2017 06:15:51 +0000	[thread overview]
Message-ID: <bug-196223-13602-U1fTJeqxBv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196223-13602@https.bugzilla.kernel.org/>

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

--- Comment #4 from Marta Löfstedt (marta.lofstedt@intel.com) ---
(In reply to Theodore Tso from comment #3)
> 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.

Doesn't help:
[  846.830596] INFO: task systemd:1 blocked for more than 120 seconds.
[  846.830705]       Tainted: G     U  W       4.12.0-rc7-next-20170630+ #3
[  846.830774] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  846.830854] systemd         D    0     1      0 0x00000000
[  846.830860] Call Trace:
[  846.830873]  __schedule+0x3c7/0x830
[  846.830880]  ? bit_wait+0x60/0x60
[  846.830884]  schedule+0x36/0x80
[  846.830889]  io_schedule+0x16/0x40
[  846.830893]  bit_wait_io+0x11/0x60
[  846.830898]  __wait_on_bit+0x58/0x90
[  846.830903]  ? submit_bio+0x73/0x150
[  846.830908]  out_of_line_wait_on_bit+0x8e/0xb0
[  846.830914]  ? bit_waitqueue+0x40/0x40
[  846.830920]  __wait_on_buffer+0x32/0x40
[  846.830926]  __ext4_get_inode_loc+0x1b3/0x400
[  846.830932]  ext4_iget+0x92/0xbc0
[  846.830938]  ext4_iget_normal+0x2f/0x40
[  846.830942]  ext4_lookup+0xea/0x270
[  846.830946]  lookup_slow+0xa5/0x160
[  846.830951]  walk_component+0x1bf/0x370
[  846.830954]  ? path_init+0x1e4/0x3a0
[  846.830958]  path_lookupat+0x73/0x220
[  846.830962]  filename_lookup+0xb8/0x1a0
[  846.830966]  ? __d_alloc+0x27/0x1d0
[  846.830972]  ? __check_object_size+0xb3/0x190
[  846.830977]  ? strncpy_from_user+0x4d/0x170
[  846.830981]  user_path_at_empty+0x36/0x40
[  846.830985]  ? user_path_at_empty+0x36/0x40
[  846.830990]  vfs_statx+0x83/0xf0
[  846.830995]  SYSC_newstat+0x3d/0x70
[  846.831001]  ? ep_read_events_proc+0xd0/0xd0
[  846.831006]  SyS_newstat+0xe/0x10
[  846.831010]  entry_SYSCALL_64_fastpath+0x1e/0xa9

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

  parent reply	other threads:[~2017-07-03  6:15 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
2017-07-03  6:15 ` bugzilla-daemon [this message]
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-U1fTJeqxBv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).