Thread (22 messages) 22 messages, 2 authors, 2019-11-08

Re: [RFC PATCH 08/14] pipe: Allow buffers to be marked read-whole-or-error for notifications [ver #2]

From: Andy Lutomirski <luto@kernel.org>
Date: 2019-11-07 18:15:43
Also in: keyrings, linux-api, linux-block, linux-fsdevel, linux-security-module, lkml

On Thu, Nov 7, 2019 at 5:39 AM David Howells [off-list ref] wrote:
Allow a buffer to be marked such that read() must return the entire buffer
in one go or return ENOBUFS.  Multiple buffers can be amalgamated into a
single read, but a short read will occur if the next "whole" buffer won't
fit.

This is useful for watch queue notifications to make sure we don't split a
notification across multiple reads, especially given that we need to
fabricate an overrun record under some circumstances - and that isn't in
the buffers.
Hmm.  I'm not totally in love with introducing a new error code like
this for read(), especially if it could affect the kind of pipe that
is bound to a file in a filesystem.  But maybe it's not a problem.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help