From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 201555] [f2fs] Processes freezing periodically with f2fs root
Date: Mon, 05 Nov 2018 03:33:43 +0000 [thread overview]
Message-ID: <bug-201555-202145-fSbuIJ67rL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201555-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201555
Chao Yu (chao@kernel.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #6 from Chao Yu (chao@kernel.org) ---
(In reply to Pierpaolo Valerio from comment #5)
> So, my office PC is still up after more than 5 days, so I'm assuming the
> problem is either solved or greatly reduced.
I guess below two commits may fix potential deadlock issue:
1) Revert: "f2fs: check last page index in cached bio to decide submission"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bab475c5414e8d1fa182fd17ae966864e9c85741
2) f2fs: submit cached bio to avoid endless PageWriteback
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=48018b4cfd07dd2df9a067fb3a6a3221c19eed11
I think you can just merge them to stable kernel with the specified version as
you wish, and then have a try.
> When can I expect to see the changes merged? Will it be in a point release
It has been merged into Linux 4.20-rc1, maybe that can be your option if you
don't want to wait 4.20 about 2 months bug fixing iteration.
> or should I wait for 4.20?
> Thanks a lot.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-11-05 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 9:02 [Bug 201555] New: [f2fs] Processes freezing periodically with f2fs root bugzilla-daemon
2018-10-31 3:31 ` [Bug 201555] " bugzilla-daemon
2018-10-31 8:02 ` bugzilla-daemon
2018-10-31 8:02 ` bugzilla-daemon
2018-10-31 12:53 ` bugzilla-daemon
2018-11-04 16:31 ` bugzilla-daemon
2018-11-05 3:33 ` bugzilla-daemon [this message]
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-201555-202145-fSbuIJ67rL@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.