[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFEAcA9BQQah2vVfnwO4-3m4eHv9QtfvjvDpTdw+SmqicsDOMA@mail.gmail.com>
Date: Mon, 20 Apr 2020 16:29:32 +0100
From: Peter Maydell <peter.maydell@...aro.org>
To: Eric Blake <eblake@...hat.com>
Cc: "Theodore Y. Ts'o" <tytso@....edu>,
Linus Walleij <linus.walleij@...aro.org>,
Linux API <linux-api@...r.kernel.org>,
QEMU Developers <qemu-devel@...gnu.org>,
Florian Weimer <fw@...eb.enyo.de>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Andy Lutomirski <luto@...nel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] fcntl: Add 32bit filesystem mode
On Mon, 20 Apr 2020 at 16:24, Eric Blake <eblake@...hat.com> wrote:
> It will be interesting to find how much code (wrongly) assumes it can
> use a blind assignment of fcntl(fd, F_SETFD, 1) and thereby accidentally
> wipes out other existing flags, when it should have instead been doing a
> read-modify-write to protect flags other than FD_CLOEXEC.
For instance, a quick grep shows 4 instances of this in QEMU :-)
thanks
-- PMM
Powered by blists - more mailing lists