From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v3] util, pasta: Add do_clone() wrapper around __clone2() and clone()
Date: Thu, 17 Nov 2022 08:24:47 +0100 [thread overview]
Message-ID: <20221117082447.7c8b787d@elisabeth> (raw)
In-Reply-To: <Y3VrkCkY12sEEj/g@yekko>
On Thu, 17 Nov 2022 10:00:32 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Wed, Nov 16, 2022 at 05:30:57PM +0100, Stefano Brivio wrote:
> > Spotted in Debian's buildd logs: on ia64, clone(2) is not available:
> > the glibc wrapper is named __clone2() and it takes, additionally,
> > the size of the stack area passed by the caller.
> >
> > Add a do_clone() wrapper handling the different cases, and also
> > taking care of pointing the child's stack in the middle of the
> > allocated area: on PA-RISC (hppa), handled by clone(), the stack
> > grows up, and on ia64 the stack grows down, but the register backing
> > store grows up -- and I think it might be actually used here.
> >
> > Suggested-by: David Gibson <david@gibson.dropbear.id.au>
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
>
> Heh, my only comment on v2 was going to be that it's not a good idea
> to name identifiers starting with _ - that's reserved for the system
> library.
Oops, yes, I keep forgetting about that -- and we already have other
offenders in util.c, I'll try to switch them to other names at some
point.
--
Stefano
prev parent reply other threads:[~2022-11-17 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:30 [PATCH v3] util, pasta: Add do_clone() wrapper around __clone2() and clone() Stefano Brivio
2022-11-16 23:00 ` David Gibson
2022-11-17 7:24 ` Stefano Brivio [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=20221117082447.7c8b787d@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).