public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alex Colomar <alx.manpages@gmail.com>
To: Jack Pearson <jack@pearson.onl>
Cc: linux-man@vger.kernel.org,
	GNU C Library <libc-alpha@sourceware.org>,
	Carlos O'Donell <carlos@redhat.com>
Subject: Re: [PATCH v2] clone.2: note EINVAL when exit_signal + bad flags
Date: Sat, 25 Feb 2023 02:04:23 +0100	[thread overview]
Message-ID: <e7f4a2ad-7b84-d678-921c-ec1e790b3614@gmail.com> (raw)
In-Reply-To: <9e2b4a99-7e68-844f-bffb-3c8efcc277fe@pearson.onl>


[-- Attachment #1.1: Type: text/plain, Size: 827 bytes --]

Hi Jack,

On 2/22/23 03:28, Jack Pearson wrote:
> Hello,
> 
> In this patch, I included my test program for the absence of this 
> behavior with
> normal `clone` per Alex's request:
> 
> https://lore.kernel.org/linux-man/fba3de52-91cc-6cbe-b4ae-7140564e9ad2@pearson.onl/T/#mde63a642e9c8d0b4e367b0a2817248e8e0b29a50
> 
> Let me know if there's anything else I should do.

Could you please resend the patch (keeping all CCs), and I'll have a 
look at it again?

Thanks for the ping,

Alex

> 
> Thanks,
> Jack
> 
> On 12/14/22 13:28, Jack Pearson wrote:
>> Document that Linux will report EINVAL when exit_signal is specified and
>> either CLONE_THREAD or CLONE_PARENT is specified.
>>
> ...

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-25  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 21:28 Jack Pearson
2023-02-22  2:28 ` Jack Pearson
2023-02-25  1:04   ` Alex Colomar [this message]
2023-02-28 23:43     ` Jack Pearson

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=e7f4a2ad-7b84-d678-921c-ec1e790b3614@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=carlos@redhat.com \
    --cc=jack@pearson.onl \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).