linux-kernel - [LSF/MM/BPF TOPIC] making O

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-next>] [day] [month] [year] [list]

Message-ID: <CAH2r5mv7Z7XmyWgp5K8ZshA1OiMBTNGU-v8FdmwwkZaNNe=4wA@mail.gmail.com>
Date:   Wed, 23 Feb 2022 23:30:07 -0600
From:   Steve French <smfrench@...il.com>
To:     lsf-pc@...ts.linux-foundation.org,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: [LSF/MM/BPF TOPIC] making O_TMPFILE more atomic

Currently creating tmpfiles on Linux can be problematic because the
tmpfile is not created and opened at the same time  (vfs_tmpfile calls
into the fs, then later vfs_open is called to open the tmpfile).   For
some filesystems it would be more natural to create and open the
tmpfile as one operation (because the action of creating the file on
some filesystems returns an open handle, so closing it then reopening
it would cause the tmpfile to be deleted).

I would like to discuss whether the function do_tmpfile (which creates
and then opens the tmpfile) could have an option for a filesystem to
do this as one operation which would allow it to be more atomic and
allow it to work on a wider variety of filesystems.

-- 
Thanks,

Steve