From: Arjun Shankar <arjun.is@lostca.se>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [PATCH] Disable warnings due to deprecated libselinux symbols used by nss and nscd
Date: Wed, 22 Jul 2020 21:07:16 +0000 [thread overview]
Message-ID: <20200722210716.GA76423@aloka.lostca.se> (raw)
In-Reply-To: <CAMe9rOpvRi5zFW2yNW1eODFywznE9Kn0dhyy0xuKgUy6TH86Dw@mail.gmail.com>
On Wed, Jul 22, 2020 at 11:47:41AM -0700, H.J. Lu wrote:
> > +/* security_context_t and sidput (along with several other symbols) were marked
> > + as deprecated by the SELinux API starting from version 3.1. We use them
> > + here, but should eventually switch to the newer API. */
> > +DIAG_PUSH_NEEDS_COMMENT
> > +DIAG_IGNORE_NEEDS_COMMENT (10, "-Wdeprecated-declarations");
> >
> > /* Check the permission from the caller (via getpeercon) to nscd.
> > Returns 0 if access is allowed, 1 if denied, and -1 on error.
> > @@ -411,6 +425,7 @@ nscd_request_avc_has_perm (int fd, request_type req)
> > rc = avc_has_perm (ssid, tsid, sc_nscd, perm, &aeref, NULL) < 0;
> >
> > out:
> > +
>
> Why this?
Thanks for catching that. It is a stray newline and needs to go.
I originally wanted to restrict the pragma to just the target of the "out:"
label, but then I moved away from that idea (there were other deprecated
symbols used in this function), and forgot to delete the newline I had added.
If this patch gets accepted without further changes, I'll remove the newline
before I commit.
next prev parent reply other threads:[~2020-07-22 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 18:38 Arjun Shankar
2020-07-22 18:47 ` H.J. Lu
2020-07-22 21:07 ` Arjun Shankar [this message]
2020-07-23 3:34 ` Carlos O'Donell
2020-07-23 4:35 ` Aurelien Jarno
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=20200722210716.GA76423@aloka.lostca.se \
--to=arjun.is@lostca.se \
--cc=aurelien@aurel32.net \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/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).