From: Guenter Roeck <linux@roeck-us.net>
To: gfs2@lists.linux.dev
Cc: Bob Peterson <rpeterso@redhat.com>,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Warning tracebacks in gfs2 with CONFIG_CGROUP_WRITEBACK=y and CONFIG_LOCKDEP=y
Date: Sat, 16 Sep 2023 19:42:17 -0700 [thread overview]
Message-ID: <5e901c35-55d7-e7fc-7191-5cdf8fd9e0cc@roeck-us.net> (raw)
Hi,
when mounting a gfs2 image on a system with CONFIG_CGROUP_WRITEBACK=y
and CONFIG_LOCKDEP=y, I get the following runtime warnings.
WARNING: CPU: 1 PID: 808 at include/linux/backing-dev.h:252 __folio_mark_dirty+0x318/0x350
WARNING: CPU: 1 PID: 808 at include/linux/backing-dev.h:252 __folio_start_writeback+0x330/0x364
WARNING: CPU: 1 PID: 808 at include/linux/backing-dev.h:252 __folio_end_writeback+0x418/0x51c
This is seen at least with v5.15.y and later (I can't mount my test file
system with older kernel branches).
I don't know if it is a problem or concern, it is just something I noticed
while running various basic file system tests.
Guenter
reply other threads:[~2023-09-17 2:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5e901c35-55d7-e7fc-7191-5cdf8fd9e0cc@roeck-us.net \
--to=linux@roeck-us.net \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=rpeterso@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).