From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 198187] jbd2_log_wait_commit hangs
Date: Wed, 24 Jan 2018 10:47:01 +0000 [thread overview]
Message-ID: <bug-198187-13602-3N9aWJnpbL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198187-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198187
--- Comment #12 from Mike Snitzer (snitzer@redhat.com) ---
(In reply to Jan Kara from comment #11)
> Thanks. Mike, any idea here? It appears JBD2 submitted IO to dm-raid1 and it
> never completed. Apparently this did not happen with 4.12.8 but it does
> happen relatively regularly with 4.13.8...
git log --oneline v4.12.8^..v4.13.8 -- drivers/md/dm-raid1.c | tac
9966afa dm: fix REQ_RAHEAD handling
846785e dm: don't return errnos from ->map
1be5690 dm: change ->end_io calling convention
4e4cbee block: switch bios to blk_status_t
So just changes from Christoph to prepare for and finally switch to
blk_status_t
$ git log --oneline v4.12.8^..v4.13.8 -- drivers/md/dm.c | tac
846785e dm: don't return errnos from ->map
1be5690 dm: change ->end_io calling convention
4e4cbee block: switch bios to blk_status_t
7e026c8 dm: add ->copy_from_iter() dax operation support
abebfbe dm: add ->flush() dax operation support
011067b blk: replace bioset_create_nobvec() with a flags arg to bioset_create()
47e0fb46 blk: make the bioset rescue_workqueue optional.
93e6442 dm: add basic support for using the select or poll function
a4aa5e5 dm: fix REQ_OP_ZONE_RESET bio handling
264c869 dm: fix REQ_OP_ZONE_REPORT bio handling
1099930 dm: introduce dm_remap_zone_report()
41341af dm: don't set bounce limit
fbd08e7 bio-integrity: fix interface for bio_integrity_trim
54385bf dm: fix the second dec_pending() argument in __split_and_process_bio()
6044078 dm: fix printk() rate limiting code
bfc0ab4 dax: remove the pmem_dax_ops->flush abstraction
666cb84 dm ioctl: fix alignment of event number in the device list
Nothing in these DM core changes stand out to me as a potential source for IO
hangs.
But obviously the devil is in the details...
Could easily be something in block core is negatively influencing DM, etc.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-01-24 10:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 12:56 [Bug 198187] New: jbd2_log_wait_commit hangs bugzilla-daemon
2017-12-18 12:57 ` [Bug 198187] " bugzilla-daemon
2017-12-18 23:39 ` bugzilla-daemon
2017-12-20 5:35 ` bugzilla-daemon
2017-12-20 5:36 ` bugzilla-daemon
2017-12-20 5:36 ` bugzilla-daemon
2017-12-20 5:40 ` bugzilla-daemon
2018-01-04 16:10 ` bugzilla-daemon
2018-01-18 6:24 ` bugzilla-daemon
2018-01-18 10:05 ` bugzilla-daemon
2018-01-18 10:33 ` bugzilla-daemon
2018-01-23 7:20 ` bugzilla-daemon
2018-01-24 10:02 ` bugzilla-daemon
2018-01-24 10:47 ` bugzilla-daemon [this message]
2019-01-02 15:00 ` bugzilla-daemon
2019-01-02 17:22 ` 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-198187-13602-3N9aWJnpbL@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).