From: Matthew Wilcox <willy@infradead.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
v9fs-developer@lists.sourceforge.net,
Sergey Alirzaev <l29ah@cock.li>
Subject: Re: [GIT PULL] 9p update for 5.7
Date: Mon, 6 Apr 2020 09:46:41 -0700 [thread overview]
Message-ID: <20200406164641.GF21484@bombadil.infradead.org> (raw)
In-Reply-To: <20200406164057.GA18312@nautica>
On Mon, Apr 06, 2020 at 06:40:57PM +0200, Dominique Martinet wrote:
> Anyway, I agree looking at O_NONBLOCK for that isn't obvious.
> I agree with the usecase here and posix allows short reads regardless of
> the flag so the behaviour is legal either way ; the filesystem is
> allowed to return whenever it wants on a whim - let's just add some docs
> as you suggest unless Sergey has something to add.
Ahahahahhahahahahaha.
POSIX may well "allow" short reads, but userspace programmers basically
never check the return value from read(). Short reads aren't actually
allowed. That's why signals are only allowed to interrupt syscalls if
they're fatal (and the application will never see the returned value
because it's already dead).
next prev parent reply other threads:[~2020-04-06 16:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 11:07 [GIT PULL] 9p update for 5.7 Dominique Martinet
2020-04-06 15:53 ` Linus Torvalds
2020-04-06 16:40 ` Dominique Martinet
2020-04-06 16:46 ` Matthew Wilcox [this message]
2020-04-06 16:55 ` Dominique Martinet
2020-04-06 17:04 ` Linus Torvalds
2020-04-06 17:39 ` Matthew Wilcox
2020-04-06 17:46 ` Linus Torvalds
2020-04-06 18:42 ` Dominique Martinet
2020-04-07 2:16 ` L29Ah
2020-04-07 6:31 ` Dominique Martinet
2020-04-07 17:59 ` Linus Torvalds
2020-04-06 16:45 ` pr-tracker-bot
2020-04-08 15:12 ` [GIT PULL v2] " Dominique Martinet
2020-04-09 4:53 ` Linus Torvalds
2020-04-09 4:55 ` 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=20200406164641.GF21484@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=asmadeus@codewreck.org \
--cc=l29ah@cock.li \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).