From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [GIT PULL] pipe: nonblocking rw for io_uring
Date: Tue, 25 Apr 2023 14:10:04 -0600 [thread overview]
Message-ID: <bdb6a832-a239-1ce4-d520-d024e0e710e7@kernel.dk> (raw)
In-Reply-To: <CAHk-=wjNfkT1oVLGbe2=Vymp66Ht=tk+YKa9gUL4T=_hA_JLjg@mail.gmail.com>
On 4/25/23 1:58?PM, Linus Torvalds wrote:
> Jens - I don't think this actually matters for the f_mode value issue,
> since the only thing that might change is that FMODE_NOWAIT bit, but I
> was clearly wrong on READ_ONCE(). So that loop should have it, just to
> have the right pattern after all.
Noted, I'll update it so it's consistent with the other use cases.
Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2023-04-25 20:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:01 [GIT PULL] pipe: nonblocking rw for io_uring Christian Brauner
2023-04-24 21:05 ` Linus Torvalds
2023-04-24 21:22 ` Jens Axboe
2023-04-24 21:37 ` Linus Torvalds
2023-04-24 21:55 ` Jens Axboe
2023-04-24 22:00 ` Linus Torvalds
2023-04-24 22:05 ` Jens Axboe
2023-04-24 22:03 ` Jens Axboe
2023-04-24 21:58 ` Linus Torvalds
2023-04-24 22:07 ` Jens Axboe
2023-04-24 22:44 ` Jens Axboe
2023-04-25 3:16 ` Linus Torvalds
2023-04-25 13:46 ` Jens Axboe
2023-04-25 17:20 ` Linus Torvalds
2023-04-25 19:49 ` Peter Zijlstra
2023-04-25 19:58 ` Linus Torvalds
2023-04-25 20:10 ` Jens Axboe [this message]
2023-04-25 20:29 ` Linus Torvalds
[not found] ` <978690c4-1d25-46e8-3375-45940ec1ea51@huaweicloud.com>
2023-05-08 8:39 ` Peter Zijlstra
2023-05-08 10:16 ` David Laight
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=bdb6a832-a239-1ce4-d520-d024e0e710e7@kernel.dk \
--to=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=will@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 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.