mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: build failure after merge of the ntfs3 tree
Date: Mon, 10 Nov 2025 10:47:14 +0100	[thread overview]
Message-ID: <033fe015-f96f-40d1-ba63-995982f7ba26@paragon-software.com> (raw)
In-Reply-To: <20251106095733.600e04ac@canb.auug.org.au>

On 11/5/25 23:57, Stephen Rothwell wrote:

> 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.
>
Hello,

Thanks for the report and for reverting it. I’ll prepare a fix for this issue.

Regards,
Konstantin


  reply	other threads:[~2025-11-10  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 22:57 Stephen Rothwell
2025-11-10  9:47 ` Konstantin Komarov [this message]
  -- 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=033fe015-f96f-40d1-ba63-995982f7ba26@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pedrodemargomes@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=yangyongpeng@xiaomi.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

all inboxes | Powered by JetHome®