From: Zach Riggle <zachriggle@gmail.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Riku Voipio <riku.voipio@iki.fi>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] linux-user: fix is_proc_myself to check the paths via realpath
Date: Fri, 10 Nov 2017 19:48:09 -0600 [thread overview]
Message-ID: <CAMP9c5kG9m-swMJBtdQPzPkjLy7zq9sEdRA-PGcdeFDAT-DH9w@mail.gmail.com> (raw)
In-Reply-To: <CAMP9c5m6GK_Xwt6z3Bj+1WauHzHffzFb1cVD9ojeh2m8gA-D8w@mail.gmail.com>
I wrote up a quick example to show that this should work specifically for
/proc/self/exe:
#define _GNU_SOURCE
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
int main(int argc, char** argv) {
int fd = open("/proc/self/exe", O_NOFOLLOW | O_PATH);
system("ls -la /proc/$PPID/fd/");
}
*Zach Riggle*
On Fri, Nov 10, 2017 at 7:47 PM, Zach Riggle <zachriggle@gmail.com> wrote:
> Good catch. Relying on realpath() for *exe* does cause issues.
>
> A better general solution (which handles the "exe" case) is to use open(2)
> with O_PATH | O_NOFOLLOW for the candidate path (e.g. /proc/self/exe) and
> to do the same for the path we're testing along with readlink().
>
> If, in the process of link resolution via the readlink() loop, we end up
> with the same path as our candidate, we can return true. This avoids the
> need to rely on any libc implementation of realpath(), since we're just
> relying on the host kernel.
>
>
> *Zach Riggle*
>
> On Fri, Nov 10, 2017 at 5:44 PM, Laurent Vivier <laurent@vivier.eu> wrote:
>
>> Le 25/10/2017 à 05:34, Zach Riggle a écrit :
>> > Previously, it was possible to get a handle to the "real" /proc/self/mem
>> > by creating a symlink to it and opening the symlink, or opening e.g.
>> > "./mem" after chdir'ing to "/proc/self".
>> >
>> > $ ln -s /proc/self self
>> > $ cat self/maps
>> > 60000000-602bc000 r-xp 00000000 fc:01 270375
>> /usr/bin/qemu-arm-static
>> > 604bc000-6050f000 rw-p 002bc000 fc:01 270375
>> /usr/bin/qemu-arm-static
>> > ...
>> >
>> > Signed-off-by: Zach Riggle <zachriggle@gmail.com>
>> > ---
>> > linux-user/syscall.c | 47 ++++++++++++++++++++++++++++--
>> -----------------
>> > 1 file changed, 28 insertions(+), 19 deletions(-)
>> >
>> > diff --git a/linux-user/syscall.c b/linux-user/syscall.c
>> > index 9bf901fa11..6c1f28a1f7 100644
>> > --- a/linux-user/syscall.c
>> > +++ b/linux-user/syscall.c
>> > @@ -7496,26 +7496,35 @@ static int open_self_auxv(void *cpu_env, int fd)
>> >
>> > static int is_proc_myself(const char *filename, const char *entry)
>> > {
>> > - if (!strncmp(filename, "/proc/", strlen("/proc/"))) {
>> > - filename += strlen("/proc/");
>> > - if (!strncmp(filename, "self/", strlen("self/"))) {
>> > - filename += strlen("self/");
>> > - } else if (*filename >= '1' && *filename <= '9') {
>> > - char myself[80];
>> > - snprintf(myself, sizeof(myself), "%d/", getpid());
>> > - if (!strncmp(filename, myself, strlen(myself))) {
>> > - filename += strlen(myself);
>> > - } else {
>> > - return 0;
>> > - }
>> > - } else {
>> > - return 0;
>> > - }
>> > - if (!strcmp(filename, entry)) {
>> > - return 1;
>> > - }
>> > + char proc_self_entry[PATH_MAX + 1];
>> > + char proc_self_entry_realpath[PATH_MAX + 1];
>> > + char filename_realpath[PATH_MAX + 1];
>> > +
>> > + if (PATH_MAX < snprintf(proc_self_entry,
>> > + sizeof(proc_self_entry),
>> > + "/proc/self/%s",
>> > + entry)) {
>> > + /* Full path to "entry" is too long to fit in the buffer */
>> > + return 0;
>> > }
>> > - return 0;
>> > +
>> > + if (!realpath(filename, filename_realpath)) {
>> > + /* File does not exist, or can't be canonicalized */
>> > + return 0;
>> > + }
>> > +
>> > + if (!realpath(proc_self_entry, proc_self_entry_realpath)) {
>> > + /* Procfs entry does not exist */
>> > + return 0;
>> > + }
>> > +
>> > + if (strcmp(filename_realpath, proc_self_entry_realpath) != 0) {
>> > + /* Paths are different */
>>
>> I think it doesn't work with /proc/map/exe (or other soft link in
>> /proc/self) as realpath will give the path of the executable and not the
>> path inside /proc so it will be true for any process with the same
>> executable (which in our case is qemu for all).
>>
>> Thanks,
>> Laurent
>>
>>
>
next prev parent reply other threads:[~2017-11-11 1:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 23:07 [Qemu-devel] [PATCH] linux-user: fix is_proc_myself to check the paths via realpath Zach Riggle
2017-10-25 2:55 ` no-reply
2017-10-25 3:34 ` [Qemu-devel] [PATCH v2] " Zach Riggle
2017-10-26 21:06 ` Zach Riggle
2017-10-27 9:36 ` Riku Voipio
2017-10-27 17:05 ` Zach Riggle
2017-10-27 19:07 ` Zach Riggle
2017-10-28 5:14 ` Eric Blake
2017-11-02 18:26 ` Zach Riggle
2017-11-02 19:35 ` Peter Maydell
2017-11-06 20:17 ` Zach Riggle
2017-11-07 20:06 ` Riku Voipio
2017-11-10 21:44 ` Zach Riggle
2017-11-10 23:44 ` Laurent Vivier
2017-11-11 1:47 ` Zach Riggle
2017-11-11 1:48 ` Zach Riggle [this message]
2017-11-14 19:44 ` Laurent Vivier
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=CAMP9c5kG9m-swMJBtdQPzPkjLy7zq9sEdRA-PGcdeFDAT-DH9w@mail.gmail.com \
--to=zachriggle@gmail.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).