From: Daniel J Walsh <dwalsh@redhat.com>
To: eparis@redhat.com
Cc: selinux@tycho.nsa.gov
Subject: [PATCH 36/74] Handle cleanup of locks properly
Date: Thu, 24 Oct 2013 10:23:23 -0400 [thread overview]
Message-ID: <52692D5B.8090706@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
restorecond has a leak which this patch fixes.
This patch looks good to me. acked.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJpLVsACgkQrlYvE4MpobMgqQCfTl70Fex73ucohJBQokMvKaZP
aV8AoM4Cu3rCbvbyKVArZBWJM+j1Qoqu
=5CDU
-----END PGP SIGNATURE-----
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0036-Handle-cleanup-of-locks-properly.patch --]
[-- Type: text/x-patch; name="0036-Handle-cleanup-of-locks-properly.patch", Size: 0 bytes --]
reply other threads:[~2013-10-24 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52692D5B.8090706@redhat.com \
--to=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--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.