public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Szabolcs Nagy via Gcc <gcc@gcc.gnu.org>
Cc: David Malcolm <dmalcolm@redhat.com>,
	 Szabolcs Nagy <szabolcs.nagy@arm.com>,
	 libc-alpha@sourceware.org
Subject: Re: Adding file descriptor attribute(s) to gcc and glibc
Date: Wed, 13 Jul 2022 14:05:46 +0200	[thread overview]
Message-ID: <877d4h1alh.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <Ys6ENUYqC2Qm5MUL@arm.com> (Szabolcs Nagy via Gcc's message of "Wed, 13 Jul 2022 09:37:09 +0100")

* Szabolcs Nagy via Gcc:

> to be honest, i'd expect interesting fd bugs to be
> dynamic and not easy to statically analyze.
> the use-after-unchecked-open maybe useful. i would
> not expect the access direction to catch many bugs.

You might be right.  But I think the annotations could help to catch
use-after-close errors.

By the way, I think it would help us if we didn't have to special-case
AT_FDCWD using inline wrappers.

Thanks,
Florian


  parent reply	other threads:[~2022-07-13 12:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 17:31 [PATCH] filedescriptor attribute Immad Mir
2022-07-12 17:33 ` Mir Immad
2022-07-12 22:16   ` Adding file descriptor attribute(s) to gcc and glibc David Malcolm
2022-07-12 22:25     ` David Malcolm
2022-07-13  8:37       ` Szabolcs Nagy
2022-07-13  8:46         ` Andreas Schwab
2022-07-13 12:05         ` Florian Weimer [this message]
2022-07-13 13:33           ` David Malcolm
2022-07-13 14:01             ` Florian Weimer
2022-07-13 16:55               ` David Malcolm
2022-07-14  8:30                 ` Szabolcs Nagy
2022-07-14 15:22                   ` David Malcolm
2022-07-14 17:07                     ` Paul Eggert
2022-07-13 16:56               ` Mir Immad
2022-07-13 19:29                 ` David Malcolm
2022-07-13 12:57         ` David Malcolm

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=877d4h1alh.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=szabolcs.nagy@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).