linux-kernel - Re: [PATCH 4/4] Return -EINVAL if userspace passes bogus flags to open()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190212203809.GK2217@ZenIV.linux.org.uk>
Date:   Tue, 12 Feb 2019 20:38:09 +0000
From:   Al Viro <viro@...iv.linux.org.uk>
To:     demiobenour@...il.com
Cc:     "open list:FILESYSTEMS (VFS and infrastructure)" 
        <linux-fsdevel@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/4] Return -EINVAL if userspace passes bogus flags to
 open()

On Tue, Feb 12, 2019 at 09:54:47AM -0500, demiobenour@...il.com wrote:
> From: "Demi M. Obenour" <demiobenour@...il.com>
> 
> While testing the O_PATHSTATIC patch, I discovered that Linux does not
> return any error if an invalid flag is passed to open(2).  This prevents
> adding new flags without a (minor) risk of breaking userspace.
> Therefore, add a check for invalid flags, and return -EINVAL if any are
> found.

... which would qualtify as userland ABI breakage all by itself.