[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240913040038.GA2825852@ZenIV>
Date: Fri, 13 Sep 2024 05:00:38 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>,
David Chinner <david@...morbit.com>,
"Darrick J. Wong" <djwong@...nel.org>, linux-xfs@...r.kernel.org,
bpf <bpf@...r.kernel.org>, Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the bpf-next tree
On Fri, Sep 13, 2024 at 01:55:51PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the bpf-next tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/xfs/xfs_exchrange.c: In function 'xfs_ioc_commit_range':
> fs/xfs/xfs_exchrange.c:938:19: error: 'struct fd' has no member named 'file'
> 938 | if (!file1.file)
> | ^
> fs/xfs/xfs_exchrange.c:940:26: error: 'struct fd' has no member named 'file'
> 940 | fxr.file1 = file1.file;
> | ^
>
> Caused by commit
>
> 1da91ea87aef ("introduce fd_file(), convert all accessors to it.")
>
> interacting with commit
>
> 398597c3ef7f ("xfs: introduce new file range commit ioctls")
>
> I have applied the following patch for today.
>
> From: Stephen Rothwell <sfr@...b.auug.org.au>
> Date: Fri, 13 Sep 2024 13:53:35 +1000
> Subject: [PATCH] fix up 3 for "introduce fd_file(), convert all accessors to
> it."
>
> interacting with commit "xfs: introduce new file range commit ioctls"
> from the xfs tree.
... and the same for io_uring/rsrc.c, conflict with "io_uring: add IORING_REGISTER_COPY_BUFFERS method".
FWIW, that (sub)series is in viro/vfs.git#for-next - I forgot to put it
there, so when bpf tree reorgs had lost their branch on top of that thing,
the conflict fixes got dropped from -next. Sorry... ;-/
Powered by blists - more mailing lists