From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] xfs_io: fix TOCTOU in openfile()
Date: Wed, 20 Feb 2019 12:50:34 +1100 [thread overview]
Message-ID: <20190220015034.GI14116@dastard> (raw)
In-Reply-To: <acf1deea-a637-571b-e501-c7cbcde95c38@redhat.com>
On Tue, Feb 19, 2019 at 05:23:38PM -0600, Eric Sandeen wrote:
> openfile() stats a path to determine whether it is a pipe, and then
> opens it with flags based on the type it saw during the stat. It's
> possible that the file at that path changes in between, and Coverity
> points this out.
>
> Instead, always open O_NONBLOCK, stat the fd we got, and turn the
> flag back off via fcntl() if it's not a pipe.
>
> Addresses-Coverity-ID: 1442788 ("Time of check time of use")
For O_NONBLOCK I think there is zero harm in the code as it stands,
but I don't really care about it tht much.
I do wonder what happens if need to conditionally use O_NONBLOCK on
open(), though....
> @@ -112,6 +106,22 @@ openfile(
> }
> }
>
> + if (fstat(fd, &st) < 0) {
> + perror("stat");
> + close(fd);
> + return -1;
> + }
> +
> + /* We only want to keep nonblocking behavior for pipes */
> + if (!S_ISFIFO(st.st_mode)) {
> + oflags &= ~O_NONBLOCK;
> + if (fcntl(fd, F_SETFL, oflags) < 0) {
Don't you need to do oflags = fcntl(fd, F_GETFL, NULL) first?
> + perror("fcntl");
> + close(fd);
> + return -1;
> + }
can you add a "goto out_close;" error jump to this function now that
this is the fourth and fifth places that have this same close/return
on error...
CHeers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-02-20 1:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 23:12 [PATCH 0/3] xfsprogs: minor 4.20 fixups Eric Sandeen
2019-02-19 23:17 ` [PATCH 1/3] xfs_io: don't pass negative len to copy_file_range_cmd Eric Sandeen
2019-02-19 23:24 ` Darrick J. Wong
2019-02-19 23:50 ` Eric Sandeen
2019-02-20 17:16 ` [PATCH v2] xfs_io: actually check copy file range helper return values Darrick J. Wong
2019-02-22 20:01 ` Anna Schumaker
2019-02-19 23:23 ` [PATCH 2/3] xfs_io: fix TOCTOU in openfile() Eric Sandeen
2019-02-20 1:50 ` Dave Chinner [this message]
2019-02-20 4:41 ` Eric Sandeen
2019-02-20 17:23 ` Darrick J. Wong
2019-02-20 20:25 ` Eric Sandeen
2019-02-19 23:33 ` [PATCH 3/3] libhandle: zero terminate fspath string Eric Sandeen
2019-02-20 17:26 ` Darrick J. Wong
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=20190220015034.GI14116@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox