From: Greg Kurz <groug@kaod.org>
To: <qemu-devel@nongnu.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>,
richard.henderson@linaro.org, qemu-stable@nongnu.org
Subject: Re: [PATCH] util/log: Close per-thread log file on thread termination
Date: Thu, 27 Oct 2022 16:36:30 +0200 [thread overview]
Message-ID: <20221027163630.4863d4be@bahia> (raw)
In-Reply-To: <20221021105734.555797-1-groug@kaod.org>
Cc'ing stable
On Fri, 21 Oct 2022 12:57:34 +0200
Greg Kurz <groug@kaod.org> wrote:
> When `-D ${logfile} -d tid` is passed, qemu_log_trylock() creates
> a dedicated log file for the current thread and opens it. The
> corresponding file descriptor is cached in a __thread variable.
> Nothing is done to close the corresponding file descriptor when the
> thread terminates though and the file descriptor is leaked.
>
> The issue was found during code inspection and reproduced manually.
>
> Fix that with an atexit notifier.
>
> Fixes: 4e51069d6793 ("util/log: Support per-thread log files")
> Cc: richard.henderson@linaro.org
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---
> util/log.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/util/log.c b/util/log.c
> index d6eb0378c3a3..39866bdaf2fa 100644
> --- a/util/log.c
> +++ b/util/log.c
> @@ -42,6 +42,7 @@ static QemuMutex global_mutex;
> static char *global_filename;
> static FILE *global_file;
> static __thread FILE *thread_file;
> +static __thread Notifier qemu_log_thread_cleanup_notifier;
>
> int qemu_loglevel;
> static bool log_append;
> @@ -77,6 +78,12 @@ static int log_thread_id(void)
> #endif
> }
>
> +static void qemu_log_thread_cleanup(Notifier *n, void *unused)
> +{
> + fclose(thread_file);
> + thread_file = NULL;
> +}
> +
> /* Lock/unlock output. */
>
> FILE *qemu_log_trylock(void)
> @@ -93,6 +100,8 @@ FILE *qemu_log_trylock(void)
> return NULL;
> }
> thread_file = logfile;
> + qemu_log_thread_cleanup_notifier.notify = qemu_log_thread_cleanup;
> + qemu_thread_atexit_add(&qemu_log_thread_cleanup_notifier);
> } else {
> rcu_read_lock();
> /*
prev parent reply other threads:[~2022-10-27 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 10:57 [PATCH] util/log: Close per-thread log file on thread termination Greg Kurz
2022-10-27 14:06 ` Paolo Bonzini
2022-10-27 14:36 ` Greg Kurz [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=20221027163630.4863d4be@bahia \
--to=groug@kaod.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.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).