From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>
Cc: Jens Axboe <axboe@kernel.dk>, David Howells <dhowells@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the block tree with the net-next tree
Date: Tue, 27 Jun 2023 12:00:43 +1000 [thread overview]
Message-ID: <20230627120043.152df5dd@canb.auug.org.au> (raw)
In-Reply-To: <20230613125939.595e50b8@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2961 bytes --]
Hi all,
On Tue, 13 Jun 2023 12:59:39 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the block tree got a conflict in:
>
> fs/splice.c
>
> between commit:
>
> 2bfc66850952 ("splice, net: Add a splice_eof op to file-ops and socket-ops")
>
> from the net-next tree and commit:
>
> 6a3f30b8bdb2 ("splice: Make do_splice_to() generic and export it")
>
> from the block tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> diff --cc fs/splice.c
> index 67ddaac1f5c5,2420ead610a7..000000000000
> --- a/fs/splice.c
> +++ b/fs/splice.c
> @@@ -969,23 -841,24 +937,35 @@@ static long do_splice_from(struct pipe_
> return out->f_op->splice_write(pipe, out, ppos, len, flags);
> }
>
> +/*
> + * Indicate to the caller that there was a premature EOF when reading from the
> + * source and the caller didn't indicate they would be sending more data after
> + * this.
> + */
> +static void do_splice_eof(struct splice_desc *sd)
> +{
> + if (sd->splice_eof)
> + sd->splice_eof(sd);
> +}
> +
> - /*
> - * Attempt to initiate a splice from a file to a pipe.
> + /**
> + * vfs_splice_read - Read data from a file and splice it into a pipe
> + * @in: File to splice from
> + * @ppos: Input file offset
> + * @pipe: Pipe to splice to
> + * @len: Number of bytes to splice
> + * @flags: Splice modifier flags (SPLICE_F_*)
> + *
> + * Splice the requested amount of data from the input file to the pipe. This
> + * is synchronous as the caller must hold the pipe lock across the entire
> + * operation.
> + *
> + * If successful, it returns the amount of data spliced, 0 if it hit the EOF or
> + * a hole and a negative error code otherwise.
> */
> - static long do_splice_to(struct file *in, loff_t *ppos,
> - struct pipe_inode_info *pipe, size_t len,
> - unsigned int flags)
> + long vfs_splice_read(struct file *in, loff_t *ppos,
> + struct pipe_inode_info *pipe, size_t len,
> + unsigned int flags)
> {
> unsigned int p_space;
> int ret;
> @@@ -1081,9 -959,9 +1070,9 @@@ ssize_t splice_direct_to_actor(struct f
> size_t read_len;
> loff_t pos = sd->pos, prev_pos = pos;
>
> - ret = do_splice_to(in, &pos, pipe, len, flags);
> + ret = vfs_splice_read(in, &pos, pipe, len, flags);
> if (unlikely(ret <= 0))
> - goto out_release;
> + goto read_failure;
>
> read_len = ret;
> sd->total_len = read_len;
This is now a conflict between the net-next tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-06-27 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 2:59 linux-next: manual merge of the block tree with the net-next tree Stephen Rothwell
2023-06-27 2:00 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-28 3:49 Stephen Rothwell
2026-04-10 12:21 Mark Brown
2026-04-10 13:51 ` Pavel Begunkov
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=20230627120043.152df5dd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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