selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Roberts <bill.c.roberts@gmail.com>
To: "Jokke Hämäläinen" <jokke.hamalainen@kolttonen.fi>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] Check strdup() failure
Date: Wed, 15 May 2019 17:36:22 -0700	[thread overview]
Message-ID: <CAFftDdpU81Kp-tF6C3tqMCZUXpXZ7nf0RQePz-THXGbRHC1x8w@mail.gmail.com> (raw)
In-Reply-To: <CAFftDdrJKk9p-Watf2M7ptMo=1L0TiEKci=LitfjqsNmkyTUMQ@mail.gmail.com>

merged: https://github.com/SELinuxProject/selinux/pull/149

On Fri, May 10, 2019 at 2:00 PM William Roberts
<bill.c.roberts@gmail.com> wrote:
>
> On Fri, May 10, 2019 at 12:04 PM Jokke Hämäläinen
> <jokke.hamalainen@kolttonen.fi> wrote:
> >
> >
> >
> > ---
> >  libselinux/utils/getconlist.c | 5 +++++
> >  1 file changed, 5 insertions(+)
> >
> > diff --git a/libselinux/utils/getconlist.c b/libselinux/utils/getconlist.c
> > index 5ac0ca85..29c16640 100644
> > --- a/libselinux/utils/getconlist.c
> > +++ b/libselinux/utils/getconlist.c
> > @@ -27,6 +27,11 @@ int main(int argc, char **argv)
> >                 switch (opt) {
> >                 case 'l':
> >                         level = strdup(optarg);
> > +                       if (!level) {
> > +                               fprintf(stderr, "memory allocation failure: %d(%s)\n",
> > +                                       errno, strerror(errno));
> > +                               return 3;
> > +                       }
> >                         break;
> >                 default:
> >                         usage(argv[0], "invalid option", 1);
> > --
> > 2.21.0
> >
>
> ack

      reply	other threads:[~2019-05-16  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 18:18 [PATCH] Check strdup() failure Jokke Hämäläinen
2019-05-10 21:00 ` William Roberts
2019-05-16  0:36   ` William Roberts [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=CAFftDdpU81Kp-tF6C3tqMCZUXpXZ7nf0RQePz-THXGbRHC1x8w@mail.gmail.com \
    --to=bill.c.roberts@gmail.com \
    --cc=jokke.hamalainen@kolttonen.fi \
    --cc=selinux@vger.kernel.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 NNTP newsgroup(s).