All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Johann Felix Soden <johfel@gmx.de>
Cc: Patrick McManus <mcmanus@ducksong.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] splice: fix problem with sys_tee and SPLICE_F_NONBLOCK
Date: Wed, 20 Feb 2008 10:35:28 +0100	[thread overview]
Message-ID: <20080220093528.GU23197@kernel.dk> (raw)
In-Reply-To: <1203457661.7758.31.camel@localhost>

On Tue, Feb 19 2008, Johann Felix Soden wrote:
> 
> Am Dienstag, den 19.02.2008, 22:25 +0100 schrieb Jens Axboe:
> > On Tue, Feb 19 2008, Johann Felix Soden wrote:
> > > > On Tue, Feb 19 2008, Johann Felix Soden wrote:
> > > > > From: Johann Felix Soden <johfel@users.sourceforge.net>
> > > > > 
> > > > > With SPLICE_F_NONBLOCK sys_tee should return number of duplicated bytes,
> > > > > not only -EAGAIN on success.
> > > > 
> > > > ?
> > > > 
> > > > The current behaviour is to return bytes tee'd, or return -EAGAIN for
> > > > zero bytes if SPLICE_F_NONBLOCK is set. It doesn't return "-EAGAIN on
> > > > success", not sure what you mean there.
> > > > 
> > > Sorry, my patch description was not correct. 
> > > 
> > > The new behavior of sys_tee with my patch is: 
> > > 	- return -EAGAIN if there are no data in the pipe, but writer
> > > 	  connected to the pipe, 
> > > 	- return 0 if there are not writers connected
> > > 	- else return number of duplicated byte 
> > > 
> > > The old behavior was: return -EAGAIN or the number (>0) of duplicated
> > > bytes.
> > 
> > Your patch has an odd way of achieving that goal, modify the real
> > location of the assignment instead of overriding something. That has the
> > potential to turn into another confusing bug later on, wondering why the
> > heck your return value isn't being passed back.
> > 
> > Improvement is welcome though, you can't distuingish -EAGAIN on the
> > input side from the output side currently.
> > 
> 
> I thought again about the problem and my patch: you are right, the patch
> is nonsense. I have learnt, that the correctness of a patch is not
> guaranteed by the (bad, but anyhow working) solution of the problem the
> patch was written for.
> Sorry for wasting your time.

Don't worry, it's not a waste of time even though your solution isn't
the correct one.

When non-blocking is set, ideally we want to return 0 if there's no hope
of anymore data and EAGAIN if trying later may yield some data. So how
about this instead?

diff --git a/fs/splice.c b/fs/splice.c
index 9b559ee..0670c91 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -1669,6 +1669,13 @@ static int link_pipe(struct pipe_inode_info *ipipe,
 		i++;
 	} while (len);
 
+	/*
+	 * return EAGAIN if we have the potential of some data in the
+	 * future, otherwise just return 0
+	 */
+	if (!ret && ipipe->waiting_writers && (flags & SPLICE_F_NONBLOCK))
+		ret = -EAGAIN;
+
 	inode_double_unlock(ipipe->inode, opipe->inode);
 
 	/*
@@ -1709,11 +1716,8 @@ static long do_tee(struct file *in, struct file *out, size_t len,
 		ret = link_ipipe_prep(ipipe, flags);
 		if (!ret) {
 			ret = link_opipe_prep(opipe, flags);
-			if (!ret) {
+			if (!ret)
 				ret = link_pipe(ipipe, opipe, len, flags);
-				if (!ret && (flags & SPLICE_F_NONBLOCK))
-					ret = -EAGAIN;
-			}
 		}
 	}
 

-- 
Jens Axboe


  reply	other threads:[~2008-02-20  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 20:14 [PATCH] splice: fix problem with sys_tee and SPLICE_F_NONBLOCK Johann Felix Soden
2008-02-19 20:25 ` Jens Axboe
2008-02-19 21:12   ` Johann Felix Soden
2008-02-19 21:25     ` Jens Axboe
2008-02-19 21:47       ` Johann Felix Soden
2008-02-20  9:35         ` Jens Axboe [this message]
2008-02-20 10:07           ` Johann Felix v. Soden-Fr.
2008-02-20 10:39             ` Jens Axboe
2008-02-20 16:31           ` Patrick McManus

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=20080220093528.GU23197@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=johfel@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcmanus@ducksong.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.