linux

iv/linux

History

Jouni Roivas 65026da59c cgroup: Zero sized write should be no-op

Do not report failure on zero sized writes, and handle them as no-op.

There's issues for example in case of writev() when there's iovec
containing zero buffer as a first one. It's expected writev() on below
example to successfully perform the write to specified writable cgroup
file expecting integer value, and to return 2. For now it's returning
value -1, and skipping the write:

	int writetest(int fd) {
	  const char *buf1 = "";
	  const char *buf2 = "1\n";
          struct iovec iov[2] = {
                { .iov_base = (void*)buf1, .iov_len = 0 },
                { .iov_base = (void*)buf2, .iov_len = 2 }
          };
	  return writev(fd, iov, 2);
	}

This patch fixes the issue by checking if there's nothing to write,
and handling the write as no-op by just returning 0.

Signed-off-by: Jouni Roivas <jouni.roivas@tuxera.com>
Signed-off-by: Tejun Heo <tj@kernel.org>

2020-09-30 13:52:06 -04:00

cgroup-internal.h

fs_parse: fold fs_parameter_desc/fs_parameter_spec

2020-02-07 14:48:37 -05:00

cgroup-v1.c

cgroup: Restructure release_agent_path handling

2020-03-12 16:44:35 -04:00

cgroup.c

cgroup: Zero sized write should be no-op

2020-09-30 13:52:06 -04:00

cpuset.c

mmap locking API: convert mmap_sem comments