From: sashiko-bot@kernel.org
To: "Max Kellermann" <max.kellermann@ionos.com>, linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: Re: [PATCH 1/3] ext4: make fast commit support optional
Date: Wed, 11 Nov 2026 13:15:13 +0000 [thread overview]
Message-ID: <sashiko-outbox-209051@kernel.org> (raw)
In-Reply-To: <20261111125242.1078620-2-max.kellermann@ionos.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] ext4: build failure exporting static inline
ext4_fc_init_inode()
--
commit 2b96da3e6bb4354cc67ea3393ddf5ce91b735978
Author: Max Kellermann <max.kellermann@ionos.com>
ext4: make fast commit support optional
This commit adds CONFIG_EXT4_FS_FAST_COMMIT to allow compiling out fast
commit support and reducing in-memory inode size.
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 8d3af062a8306..34843fcc1008b 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
[ ... ]
> @@ -3109,6 +3123,55 @@ void ext4_fc_destroy_dentry_cache(void);
> int ext4_fc_record_regions(struct super_block *sb, int ino,
> ext4_lblk_t lblk, ext4_fsblk_t pblk,
> int len, int replay);
> +#else
> +static inline bool ext4_fc_inode_tracked(struct inode *inode)
> +{
> + return false;
> +}
> +
> +static inline void ext4_fc_init(struct super_block *sb, journal_t *journal) {}
> +static inline void ext4_fc_init_inode(struct inode *inode) {}
[Severity: Medium]
Does making ext4_fc_init_inode() a static inline stub break the build when
CONFIG_EXT4_FS_FAST_COMMIT is disabled and CONFIG_EXT4_KUNIT_TESTS is
enabled?
fs/ext4/mballoc.c unconditionally exports ext4_fc_init_inode() for KUnit
tests:
fs/ext4/mballoc.c:
...
EXPORT_SYMBOL_FOR_EXT4_TEST(mb_set_bits);
EXPORT_SYMBOL_FOR_EXT4_TEST(ext4_fc_init_inode);
EXPORT_SYMBOL_FOR_EXT4_TEST(ext4_mb_mark_context);
#endif
With CONFIG_EXT4_FS_FAST_COMMIT=n, exporting the static inline function
causes a static/non-static declaration conflict or fails in modpost with a
local symbol export error.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111125242.1078620-1-max.kellermann@ionos.com?part=1
next prev parent reply other threads:[~2026-11-11 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 12:52 [PATCH 0/3] ext4: reduce per-inode memory overhead Max Kellermann
2026-11-11 12:52 ` [PATCH 1/3] ext4: make fast commit support optional Max Kellermann
2026-11-11 13:15 ` sashiko-bot [this message]
2026-11-11 13:44 ` Max Kellermann
2026-11-11 12:52 ` [PATCH 2/3] ext4: make bigalloc " Max Kellermann
2026-11-11 13:12 ` sashiko-bot
2026-11-11 12:52 ` [PATCH 3/3] ext4: store creation time in separate seconds and nanoseconds Max Kellermann
2026-11-11 13:09 ` sashiko-bot
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=sashiko-outbox-209051@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tytso@mit.edu \
/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.