linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Pipe FMODE_NOWAIT support
Date: Sat, 6 May 2023 04:33:17 -0600	[thread overview]
Message-ID: <26aba1b5-8393-a20a-3ce9-f82425673f4d@kernel.dk> (raw)

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


             reply	other threads:[~2023-05-06 10:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 10:33 Jens Axboe [this message]
2023-05-06 15:27 ` [GIT PULL] Pipe FMODE_NOWAIT support Linus Torvalds
2023-05-06 22:28   ` Jens Axboe
2023-05-07  0:55     ` Linus Torvalds
2023-05-07 10:01       ` Harald Arnesen
2023-05-06 15:46 ` pr-tracker-bot

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=26aba1b5-8393-a20a-3ce9-f82425673f4d@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).