From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203317] WARNING: CPU: 2 PID: 925 at fs/ext4/inode.c:3897 ext4_set_page_dirty+0x39/0x50
Date: Wed, 14 Aug 2019 16:36:28 +0000 [thread overview]
Message-ID: <bug-203317-13602-VsdkJSxwmO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203317-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203317
--- Comment #5 from howaboutsynergy is abandoned account everywhere (howaboutsynergy@pm.me) ---
Just to be clear, this is a regression that commit
aa56a292ce623734ddd30f52d73f527d1f3529b5 introduces, which is manifested by a
deadlock-like system freeze which is different than the one that le9g.patch is
addressing. (all of this is mentioned in prev. comment)
I don't know what the fix is, but temporarily reverting that commit gets rid of
the regression.
Please let me know whether I should stick around if you want me to test any new
patch about this or not. (because otherwise I won't even check my
email/notifications for this account, anymore)
Cheers.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-08-14 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 7:58 [Bug 203317] New: WARNING: CPU: 2 PID: 925 at fs/ext4/inode.c:3897 ext4_set_page_dirty+0x39/0x50 bugzilla-daemon
2019-07-08 13:50 ` [Bug 203317] " bugzilla-daemon
2019-07-08 14:16 ` bugzilla-daemon
2019-07-20 16:53 ` bugzilla-daemon
2019-08-14 0:13 ` bugzilla-daemon
2019-08-14 16:36 ` bugzilla-daemon [this message]
2019-09-09 0:01 ` bugzilla-daemon
2019-09-09 8:09 ` bugzilla-daemon
2019-09-09 8:19 ` bugzilla-daemon
2019-09-09 8:39 ` bugzilla-daemon
2019-09-09 9:25 ` bugzilla-daemon
2019-09-09 9:36 ` bugzilla-daemon
2019-09-09 9:50 ` bugzilla-daemon
2019-09-09 10:32 ` 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-203317-13602-VsdkJSxwmO@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.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.