From: Joshua Brindle <method@manicmethod.com>
To: Eric Paris <eparis@redhat.com>
Cc: selinux@tycho.nsa.gov, jmorris@namei.org, sds@tycho.nsa.gov
Subject: Re: [PATCH 1/3] SELinux: standardize return code handling in policydb.c
Date: Fri, 23 Apr 2010 09:16:12 -0400 [thread overview]
Message-ID: <4BD19D9C.4090306@manicmethod.com> (raw)
In-Reply-To: <20100422173632.23830.10834.stgit@paris.rdu.redhat.com>
Eric Paris wrote:
> policydb.c has lots of different standards on how to handle return paths on
> error. For the most part transition to
>
> rc=errno
> if (failure)
> goto out;
> [...]
> out:
> cleanup()
> return rc;
>
> Instead of doing cleanup mid function, or having multiple returns or other
> options. This doesn't do that for every function, but most of the complex
> functions which have cleanup routines on error.
>
Any chance the same fixes could be made in libsepol policydb.c? :)
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-04-23 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 17:36 [PATCH 1/3] SELinux: standardize return code handling in policydb.c Eric Paris
2010-04-22 17:36 ` [PATCH 2/3] SELinux: standardize return code handling in selinuxfs.c Eric Paris
2010-04-22 17:36 ` [PATCH 3/3] " Eric Paris
2010-04-22 18:25 ` Eric Paris
2010-04-22 22:30 ` James Morris
2010-04-22 22:44 ` [PATCH 1/3] SELinux: standardize return code handling in policydb.c James Morris
2010-04-23 2:37 ` Eric Paris
2010-04-23 13:16 ` Joshua Brindle [this message]
2010-04-23 13:53 ` Eric Paris
2010-04-27 15:12 ` Stephen Smalley
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=4BD19D9C.4090306@manicmethod.com \
--to=method@manicmethod.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.