From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Anton Altaparmakov <anton@tuxera.com>,
Joel Stanley <joel@jms.id.au>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: linux-next: build failure after merge of almost all the trees
Date: Tue, 2 Nov 2021 14:11:50 +0100 [thread overview]
Message-ID: <CAK8P3a39gZLWdh03_mL51qj6w+LYSPQ+T+d0t4wn8zgeSPhtqg@mail.gmail.com> (raw)
In-Reply-To: <20211102231937.2fe27ba6@canb.auug.org.au>
On Tue, Nov 2, 2021 at 1:19 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Tue, 2 Nov 2021 23:13:07 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > On Tue, 2 Nov 2021 08:06:10 +0100 Arnd Bergmann <arnd@arndb.de> wrote:
> > > On Tue, Nov 2, 2021 at 7:44 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > It does need to be changed a bit as I realized it depends on a rework of
> > > the Kconfig logic that I had in my randconfig build tree to have a common
> > > page size symbol across architectures. Without my other patch, it also
> > > needs to check for PPC_64K_PAGES.
> > >
> > > Should I send an updated version of the patch?
> >
> > That would be good, thanks.
> >
> > Even better would be to split up the function some how, but having had
> > a bit of a look at it, that may be a much longer job.
Yes, that was my initial conclusion when I looked at the code trying to
redo that loop.
> > I am assuming
> > that allocations (or their failure) are out of the question in that
> > particular function.
>
> Looking again, we probably just need to disable CONFIG_NTFS_RW ...
Ah right, that would work as well. Another possibility would be
to change NTFS_BLOCK_SIZE to 4096, at least in the affected configurations.
According to the documentation I linked to in my commit, file system images
with smaller block sizes should be extremely rare, but I have no idea if the
code would work correctly for normal images after that change.
Arnd
next prev parent reply other threads:[~2021-11-02 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 10:26 linux-next: build failure after merge of almost all the trees Stephen Rothwell
2021-10-28 12:38 ` Stephen Rothwell
2021-11-02 6:44 ` Stephen Rothwell
2021-11-02 7:06 ` Arnd Bergmann
2021-11-02 12:13 ` Stephen Rothwell
2021-11-02 12:19 ` Stephen Rothwell
2021-11-02 13:11 ` Arnd Bergmann [this message]
2021-11-03 4:47 ` 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=CAK8P3a39gZLWdh03_mL51qj6w+LYSPQ+T+d0t4wn8zgeSPhtqg@mail.gmail.com \
--to=arnd@arndb.de \
--cc=anton@tuxera.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).