From: Victor Kirhenshtein <victor@radensolutions.com>
To: xen-devel@lists.xen.org
Subject: [BUG] libxl_ctx_free calls close(0)
Date: Thu, 20 Jul 2017 20:36:28 +0300 [thread overview]
Message-ID: <1500572188.3939.15.camel@radensolutions.com> (raw)
Hello,
it seems that libxl_ctx_free always calls close(0) for some
reason, even if libxl never opens file descriptor 0. It sometimes
closes valid descriptor in application causing random and
hard to debug I/O errors.
The following simple program can be used to reproduce this bug:
#include <stdio.h>
#include <libxl.h>
static void LogMessage(struct xentoollog_logger *logger,
xentoollog_level level,
int errnoval /* or -1 */,
const char *context /* eg "xc", "xl", may be 0 */,
const char *format /* without level, context, \n
*/,
va_list al)
{
}
static void LogProgress(struct xentoollog_logger *logger,
const char *context /* see above */,
const char *doing_what /* no \r,\n */,
int percent, unsigned long done, unsigned long
total)
{
}
static void LogDestroy(struct xentoollog_logger *logger)
{
}
int main(int argc, char *argv[])
{
xentoollog_logger logger;
logger.vmessage = LogMessage;
logger.progress = LogProgress;
logger.destroy = LogDestroy;
libxl_ctx *ctx;
int rc = libxl_ctx_alloc(&ctx, LIBXL_VERSION, 0, &logger);
if (rc != 0)
{
printf("libxl_ctx_alloc failed (%d)\n", rc);
return 1;
}
libxl_ctx_free(ctx);
return 0;
}
Strace output for it is following (I omit shared library
loading on startup):
set_tid_address(0x7f787db29a50) = 17944
set_robust_list(0x7f787db29a60, 24) = 0
rt_sigaction(SIGRTMIN, {0x7f787c4809b0, [], SA_RESTORER|SA_SIGINFO,
0x7f787c489890}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x7f787c480a40, [],
SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x7f787c489890}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY})
= 0
brk(0) = 0x156d000
brk(0x158e000) = 0x158e000
pipe([3, 4]) = 0
fcntl(3, F_GETFL) = 0 (flags O_RDONLY)
fcntl(3, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
fcntl(4, F_GETFL) = 0x1 (flags O_WRONLY)
fcntl(4, F_SETFL, O_WRONLY|O_NONBLOCK) = 0
open("/proc/xen/privcmd", O_RDWR) = 5
fcntl(5, F_GETFD) = 0
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
stat("/var/run/xenstored/socket", {st_mode=S_IFSOCK|0600, st_size=0,
...}) = 0
socket(PF_LOCAL, SOCK_STREAM, 0) = 6
fcntl(6, F_GETFD) = 0
fcntl(6, F_SETFD, FD_CLOEXEC) = 0
connect(6, {sa_family=AF_LOCAL, sun_path="/var/run/xenstored/socket"},
110) = 0
close(5) = 0
close(6) = 0
close(3) = 0
close(4) = 0
close(0) = 0
exit_group(0) = ?
+++ exited with 0 +++
Best regards,
Victor Kirhenshtein
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-07-20 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 17:36 Victor Kirhenshtein [this message]
2017-07-21 8:20 ` [BUG] libxl_ctx_free calls close(0) Wei Liu
2017-07-21 10:18 ` Victor Kirhenshtein
2017-07-21 10:20 ` Wei Liu
2017-07-24 10:10 ` Ian Jackson
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=1500572188.3939.15.camel@radensolutions.com \
--to=victor@radensolutions.com \
--cc=xen-devel@lists.xen.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).