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: Mon, 09 Sep 2019 08:09:05 +0000 [thread overview]
Message-ID: <bug-203317-13602-L2dpBZ4xob@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 #7 from Theodore Tso (tytso@mit.edu) ---
Note that you filed this bug against the ext4 file system (because of the ext4
warning). As a result, regressions about the i915 driver are not going to be
seen by the i915 driver developers (and ext4 developers will generally ignroe
them).
It looks like you are trying to stress test Linux kernels under very high
memory pressure, and this is no doubt going to cause multiple issues to pop
out. Please don't conflate them into a single bug, and please note that not
all kernel subsystems (not even a majority) prefer to use bugzilla for people
to report bugs.
If you can't find a component in the bugzilla (and perhaps even if you can),
you are better off sending a note to the mailing list entry (L:) in the
MAINTAINERS file.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-09-09 8:09 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
2019-09-09 0:01 ` bugzilla-daemon
2019-09-09 8:09 ` bugzilla-daemon [this message]
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-L2dpBZ4xob@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 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).