From: Mathias Krause <mathias.krause@secunet.com>
To: lvm-devel@redhat.com
Subject: [PATCHv2] libdm: mark control fd as close-on-exec
Date: Wed, 19 Aug 2015 15:42:18 +0200 [thread overview]
Message-ID: <55D487BA.6030504@secunet.com> (raw)
In-Reply-To: <1436945698-18193-1-git-send-email-mathias.krause@secunet.com>
On 15.07.2015 09:34, Mathias Krause wrote:
> The control fd should be marked as close-on-exec to avoid file
> descriptor leaks in forking applications executing other programs.
>
> Signed-off-by: Mathias Krause <mathias.krause@secunet.com>
>
> ---
> v2: fix return value mix-up (should be 1 on success)
> ---
> libdm/ioctl/libdm-iface.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/libdm/ioctl/libdm-iface.c b/libdm/ioctl/libdm-iface.c
> index e3b33b805e93..0f9e98a4a061 100644
> --- a/libdm/ioctl/libdm-iface.c
> +++ b/libdm/ioctl/libdm-iface.c
> @@ -385,11 +385,24 @@ static void _close_control_fd(void)
> #ifdef DM_IOCTLS
> static int _open_and_assign_control_fd(const char *control)
> {
> +#ifdef O_CLOEXEC
> + /*
> + * O_CLOEXEC is supported since v2.6.23, so this may fail on old
> + * kernels. Nonetheless favour it to a two staged approach as it's
> + * atomic.
> + */
> + if ((_control_fd = open(control, O_RDWR | O_CLOEXEC)) >= 0)
> + return 1;
> +#endif
> +
> if ((_control_fd = open(control, O_RDWR)) < 0) {
> log_sys_error("open", control);
> return 0;
> }
>
> + if (fcntl(_control_fd, F_SETFD, FD_CLOEXEC))
> + log_sys_error("fcntl", "setting FD_CLOEXEC");
> +
> return 1;
> }
> #endif
Ping? Any objections to the patch?
Regards,
Mathias
next prev parent reply other threads:[~2015-08-19 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 7:34 [PATCHv2] libdm: mark control fd as close-on-exec Mathias Krause
2015-08-19 13:42 ` Mathias Krause [this message]
2015-08-27 12:02 ` Zdenek Kabelac
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=55D487BA.6030504@secunet.com \
--to=mathias.krause@secunet.com \
--cc=lvm-devel@redhat.com \
/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.