From: Andreas Gruenbacher <agruenba@redhat.com>
To: cgroups@vger.kernel.org
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Jan Kara <jack@suse.cz>, Rafael Aquini <aquini@redhat.com>,
gfs2@lists.linux.dev, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] Fix false warning in inode_to_wb
Date: Sat, 12 Apr 2025 18:39:10 +0200 [thread overview]
Message-ID: <20250412163914.3773459-1-agruenba@redhat.com> (raw)
Changes in v3:
- In gfs2_fill_super(), initialize sdp->sd_inode after initializing
->s_blocksize_bits so that ->i_blkbits will be set correctly.
- inode_to_wb(const struct inode *inode) no longer calls
inode_cgwb_enabled(struct inode *inode), so its argument can remain
const.
Changes in v2:
- In inode_to_wb(), only check if the SB_I_CGROUPWB flag is set so that
the consistency checks remain active even when cgroup writeback isn't
actively used.
- When new_inode() fails in gfs2_fill_super(), clean up correctly.
- Improve the description of "gfs2: replace sd_aspace with sd_inode".
Andreas Gruenbacher (1):
gfs2: replace sd_aspace with sd_inode
Jan Kara (1):
writeback: Fix false warning in inode_to_wb()
fs/gfs2/glock.c | 3 +--
fs/gfs2/glops.c | 4 ++--
fs/gfs2/incore.h | 9 ++++++++-
fs/gfs2/meta_io.c | 2 +-
fs/gfs2/meta_io.h | 4 +---
fs/gfs2/ops_fstype.c | 31 ++++++++++++++++++-------------
fs/gfs2/super.c | 2 +-
include/linux/backing-dev.h | 1 +
8 files changed, 33 insertions(+), 23 deletions(-)
--
2.48.1
next reply other threads:[~2025-04-12 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 16:39 Andreas Gruenbacher [this message]
2025-04-12 16:39 ` [PATCH v3 1/2] gfs2: replace sd_aspace with sd_inode Andreas Gruenbacher
2025-04-12 16:39 ` [PATCH v3 2/2] writeback: Fix false warning in inode_to_wb() Andreas Gruenbacher
2025-04-14 13:55 ` Jan Kara
2025-04-14 21:47 ` Andrew Morton
2025-04-14 23:18 ` Andreas Gruenbacher
2025-04-14 21:51 ` Andrew Morton
2025-04-14 23:22 ` Andreas Gruenbacher
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=20250412163914.3773459-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=aquini@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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