From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software•com>
Cc: Pedro Demarchi Gomes <pedrodemargomes@gmail•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Christian Brauner <brauner@kernel•org>,
Yongpeng Yang <yangyongpeng@xiaomi•com>
Subject: linux-next: build failure after merge of the ntfs3 tree
Date: Thu, 6 Nov 2025 09:57:33 +1100 [thread overview]
Message-ID: <20251106095733.600e04ac@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
Hi all,
After merging the ntfs3 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
fs/ntfs3/super.c: In function 'ntfs_init_from_boot':
fs/ntfs3/super.c:951:9: error: ignoring return value of 'sb_min_blocksize' declared with attribute 'warn_unused_result' [-Werror=unused-result]
951 | sb_min_blocksize(sb, PAGE_SIZE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Caused by commit
c1b61f715e4d ("ntfs: set dummy blocksize to read boot_block when mounting")
Exposed by commit
8637fa89e678 ("block: add __must_check attribute to sb_min_blocksize()")
from the vfs-brauner-fixes tree.
I have reverted that commit from the ntfs3 tree for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-11-05 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 22:57 Stephen Rothwell [this message]
2025-11-10 9:47 ` linux-next: build failure after merge of the ntfs3 tree Konstantin Komarov
-- strict thread matches above, loose matches on Subject: below --
2026-01-26 13:07 Mark Brown
2022-11-14 23:17 Stephen Rothwell
2022-11-17 8:56 ` Christian Brauner
2022-11-17 10:04 ` Stephen Rothwell
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=20251106095733.600e04ac@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=almaz.alexandrovich@paragon-software$(echo .)com \
--cc=brauner@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pedrodemargomes@gmail$(echo .)com \
--cc=yangyongpeng@xiaomi$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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