From: Dominique Martinet <asmadeus@codewreck.org>
To: Matthew Wilcox <willy@infradead.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 18:55:06 +0200 [thread overview]
Message-ID: <20200406165506.GA26216@nautica> (raw)
In-Reply-To: <20200406164641.GF21484@bombadil.infradead.org>
Matthew Wilcox wrote on Mon, Apr 06, 2020:
> 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).
I've seen tons of programs not check read return value yes but these
also have no idea what O_NONBLOCK is so I'm not sure how realistic a
use-case that is?
The alternative I see would be making pipes go through the server as I
said, but that would probably mean another mount option for this; pipes
work as local pipes like they do in nfs currently.
--
Dominique
next prev parent reply other threads:[~2020-04-06 16:55 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
2020-04-06 16:55 ` Dominique Martinet [this message]
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=20200406165506.GA26216@nautica \
--to=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 \
--cc=willy@infradead.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.