Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20190207154519.8635-1-kaslevs@vmware.com> <20190213094445.1774f959@gandalf.local.home>
 <20190219121212.6c46b979@gandalf.local.home> <20190304105836.33f80dc3@gandalf.local.home>
In-Reply-To: <20190304105836.33f80dc3@gandalf.local.home>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Mon, 4 Mar 2019 16:04:11 -0800
Message-ID: <CAHk-=wipy3J4r-dLim3QvNA2jVPi2uPCi=rTDiMYikBi5OiKnQ@mail.gmail.com>
Subject: Re: [RFC PATCH] fs: Make splice() and tee() take into account
 O_NONBLOCK flag on pipes
To:     Steven Rostedt <rostedt@goodmis.org>
Cc:     Alexander Viro <viro@zeniv.linux.org.uk>,
        Jens Axboe <axboe@kernel.dk>,
        Slavomir Kaslev <kaslevs@vmware.com>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Mar 4, 2019 at 7:58 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> I'm still just hearing crickets about this? Should I just send this
> directly to Linus or Andrew?

I'll take it. It looks sane.

Of course, if it turns out that this breaks something that assumes
that splice blocks purely based on the SPLICE_F_NONBLOCK flag, we'll
have to revert it. Looking at the history of splice, it does look like
it has always ignored O_NONBLOCK.

                 Linus