From: Joe Simmons-Talbott <josimmon@redhat.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] posix: Deprecate group_member for Linux
Date: Mon, 16 Oct 2023 12:52:00 -0400 [thread overview]
Message-ID: <20231016165200.GQ4098455@oak> (raw)
In-Reply-To: <4b80d08c6263790f1694085c0f5a862c883fbd67.camel@xry111.site>
On Wed, Oct 04, 2023 at 09:06:03PM +0800, Xi Ruoyao wrote:
> On Thu, 2023-09-21 at 12:20 -0400, Joe Simmons-Talbott wrote:
> > diff --git a/sysdeps/unix/sysv/linux/group_member.h b/sysdeps/unix/sysv/linux/group_member.h
> > new file mode 100644
> > index 0000000000..9b24569d4e
> > --- /dev/null
> > +++ b/sysdeps/unix/sysv/linux/group_member.h
> > @@ -0,0 +1,27 @@
> > +/* Copyright (C) 2023 Free Software Foundation, Inc.
> > + This file is part of the GNU C Library.
> > +
> > + The GNU C Library is free software; you can redistribute it and/or
> > + modify it under the terms of the GNU Lesser General Public
> > + License as published by the Free Software Foundation; either
> > + version 2.1 of the License, or (at your option) any later version.
> > +
> > + The GNU C Library is distributed in the hope that it will be useful,
> > + but WITHOUT ANY WARRANTY; without even the implied warranty of
> > + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> > + Lesser General Public License for more details.
> > +
> > + You should have received a copy of the GNU Lesser General Public
> > + License along with the GNU C Library; if not, see
> > + <https://www.gnu.org/licenses/>. */
> > +
> > +#ifndef _GROUP_MEMBER_H
> > +#define _GROUP_MEMBER_H 1
> > +
> > +#ifdef __USE_GNU
> > +/* Return nonzero iff the calling process is in group GID. Deprecated */
> > +extern int group_member (__gid_t __gid) __THROW
> > + __attribute_deprecated__;
>
> Maybe `__attribute_deprecated_msg__ ("may overflow the stack")` is
> better? And should we have an alternate interface to replace it?
I'll add your suggestion in v2. There is opposition to adding a
replacement group_member interface since it would require converting
from a boolean interface to a tri-state interface which are difficult
for programmers.
Thanks,
Joe
prev parent reply other threads:[~2023-10-16 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 16:20 Joe Simmons-Talbott
2023-10-04 12:56 ` Joe Simmons-Talbott
2023-10-04 13:06 ` Xi Ruoyao
2023-10-04 14:18 ` Cristian Rodríguez
2023-10-16 17:00 ` Joe Simmons-Talbott
2023-10-16 16:52 ` Joe Simmons-Talbott [this message]
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=20231016165200.GQ4098455@oak \
--to=josimmon@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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).