From: "Rainer Müller" <raimue@codingfarm.de>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v2] linux-user: Use memfd for open syscall emulation
Date: Fri, 29 Jul 2022 23:19:17 +0200 [thread overview]
Message-ID: <dd5df8a5-c406-43a0-7557-0c1653f70de6@codingfarm.de> (raw)
In-Reply-To: <d03974ec-4b8b-2ba2-cfe8-5c235d937b76@linaro.org>
On 29/07/2022 18.01, Richard Henderson wrote:
> On 7/29/22 08:49, Rainer Müller wrote:
>> + /* create temporary file to map stat to */
>> + tmpdir = getenv("TMPDIR");
>> + if (!tmpdir)
>> + tmpdir = "/tmp";
>> + snprintf(filename, sizeof(filename),
>> "%s/qemu-open.XXXXXX", tmpdir);
>> + fd = mkstemp(filename);
>> + if (fd < 0) {
>> + return fd;
>> + }
>
> We've been using g_file_open_tmp elsewhere; probably good to follow suit
> here.
That seemed reasonable at first, but with regards to error handling it
gets a bit complicated.
The suggested g_file_open_tmp() would leave us with a GError only, but
to return something meaningful to the caller we must set errno in this
context. As far as I can see, there is no way to convert back to an
errno from GError.
With g_file_open_tmp() we could always set the same generic errno, but
that would hide the real cause completely. I debugged this problem with
this message that was confusing, but at least it gave away a hint:
cat: can't open '/proc/self/stat': Read-only file system
The other option would be to g_assert_true(fd >= 0) and kill the process
in case opening the temporary file failed. This also feels wrong, as the
caller could still recover from this state and continue.
Rainer
next prev parent reply other threads:[~2022-07-29 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 16:28 [PATCH] linux-user: Use memfd for open syscall emulation Rainer Müller
2022-07-25 18:37 ` Richard Henderson
2022-07-29 15:49 ` [PATCH v2] " Rainer Müller
2022-07-29 16:01 ` Richard Henderson
2022-07-29 21:19 ` Rainer Müller [this message]
2022-07-29 21:29 ` Richard Henderson
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=dd5df8a5-c406-43a0-7557-0c1653f70de6@codingfarm.de \
--to=raimue@codingfarm.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@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).