Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <26aba1b5-8393-a20a-3ce9-f82425673f4d@kernel.dk>
Date:   Sat, 6 May 2023 04:33:17 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.0
Content-Language: en-US
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
From:   Jens Axboe <axboe@kernel.dk>
Subject: [GIT PULL] Pipe FMODE_NOWAIT support
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Linus,

Here's the revised edition of the FMODE_NOWAIT support for pipes, in
which we just flag it as such supporting FMODE_NOWAIT unconditionally,
but clear it if we ever end up using splice/vmsplice on the pipe. The
pipe read/write side is perfectly fine for nonblocking IO, however
splice and vmsplice can potentially wait for IO with the pipe lock held.

Please pull!


The following changes since commit 457391b0380335d5e9a5babdec90ac53928b23b4:

  Linux 6.3 (2023-04-23 12:02:52 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/pipe-nonblock-2023-05-06

for you to fetch changes up to afed6271f5b0d78ca1a3739c1da4aa3629b26bba:

  pipe: set FMODE_NOWAIT on pipes (2023-04-25 14:08:59 -0600)

----------------------------------------------------------------
pipe-nonblock-2023-05-06

----------------------------------------------------------------
Jens Axboe (2):
      splice: clear FMODE_NOWAIT on file if splice/vmsplice is used
      pipe: set FMODE_NOWAIT on pipes

 fs/pipe.c   |  3 +++
 fs/splice.c | 34 ++++++++++++++++++++++++++++++----
 2 files changed, 33 insertions(+), 4 deletions(-)

-- 
Jens Axboe