Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Eric Biggers <ebiggers3@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Joe Lawrence <joe.lawrence@redhat.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Willy Tarreau <w@1wt.eu>, Mikulas Patocka <mpatocka@redhat.com>,
"Luis R . Rodriguez" <mcgrof@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] pipe: buffer limits fixes and cleanups
Date: Thu, 11 Jan 2018 12:36:15 -0800 [thread overview]
Message-ID: <CAGXu5jKZ7A0ajSrAnvQ_25VgNQuy+Ti+VVuWqP0bRqGkknQH0A@mail.gmail.com> (raw)
In-Reply-To: <20180111052902.14409-1-ebiggers3@gmail.com>
On Wed, Jan 10, 2018 at 9:28 PM, Eric Biggers <ebiggers3@gmail.com> wrote:
> This series simplifies the sysctl handler for pipe-max-size and fixes
> another set of bugs related to the pipe buffer limits:
>
> - The root user wasn't allowed to exceed the limits when creating new
> pipes.
>
> - There was an off-by-one error when checking the limits, so a limit of
> N was actually treated as N - 1.
>
> - F_SETPIPE_SZ accepted values over UINT_MAX.
>
> - Reading the pipe buffer limits could be racy.
>
> Changed since v1:
>
> - Added "Fixes" tag to "pipe: fix off-by-one error when checking buffer limits"
> - In pipe_set_size(), checked 'nr_pages' rather than 'size'
> - Fixed commit message for "pipe: simplify round_pipe_size()"
Thanks for the fixes! This looks good to me. Please consider the whole series:
Acked-by: Kees Cook <keescook@chromium.org>
-Kees
>
> Eric Biggers (7):
> pipe, sysctl: drop 'min' parameter from pipe-max-size converter
> pipe, sysctl: remove pipe_proc_fn()
> pipe: actually allow root to exceed the pipe buffer limits
> pipe: fix off-by-one error when checking buffer limits
> pipe: reject F_SETPIPE_SZ with size over UINT_MAX
> pipe: simplify round_pipe_size()
> pipe: read buffer limits atomically
>
> fs/pipe.c | 57 ++++++++++++++++++++---------------------------
> include/linux/pipe_fs_i.h | 5 ++---
> include/linux/sysctl.h | 3 ---
> kernel/sysctl.c | 33 +++++----------------------
> 4 files changed, 32 insertions(+), 66 deletions(-)
>
> --
> 2.15.1
>
--
Kees Cook
Pixel Security
next prev parent reply other threads:[~2018-01-11 20:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 5:28 Eric Biggers
2018-01-11 5:28 ` [PATCH v2 1/7] pipe, sysctl: drop 'min' parameter from pipe-max-size converter Eric Biggers
2018-01-11 5:28 ` [PATCH v2 2/7] pipe, sysctl: remove pipe_proc_fn() Eric Biggers
2018-01-11 5:28 ` [PATCH v2 3/7] pipe: actually allow root to exceed the pipe buffer limits Eric Biggers
2018-01-11 5:28 ` [PATCH v2 4/7] pipe: fix off-by-one error when checking " Eric Biggers
2018-01-11 5:29 ` [PATCH v2 5/7] pipe: reject F_SETPIPE_SZ with size over UINT_MAX Eric Biggers
2018-01-11 5:29 ` [PATCH v2 6/7] pipe: simplify round_pipe_size() Eric Biggers
2018-01-11 5:29 ` [PATCH v2 7/7] pipe: read buffer limits atomically Eric Biggers
2018-01-11 20:36 ` Kees Cook [this message]
2018-01-11 21:41 ` [PATCH v2 0/7] pipe: buffer limits fixes and cleanups Joe Lawrence
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=CAGXu5jKZ7A0ajSrAnvQ_25VgNQuy+Ti+VVuWqP0bRqGkknQH0A@mail.gmail.com \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=ebiggers3@gmail.com \
--cc=joe.lawrence@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mpatocka@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=w@1wt.eu \
--subject='Re: [PATCH v2 0/7] pipe: buffer limits fixes and cleanups' \
/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
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).