All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Stephen Bertram <sbertram@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3] Add new tests for clone and clone3
Date: Tue, 18 Nov 2025 15:54:45 +0100	[thread overview]
Message-ID: <20251118145445.GA45810@pevik> (raw)
In-Reply-To: <CAD_=S2=jJFLvESH9c0-a41-tTKFDQDovX3T47af7-2WXmH8rgw@mail.gmail.com>

Hi Stephen,
...
> > > +/*\
> > > + * This test verifies that clone() fals with EPERM when CAP_SYS_ADMIN
> > s/fals/fails/

> > If new version is needed, could you please use :man2:`clone` ?
> > This will link man clone(2) [2] in our test catalog [3].

> So I'm clear, a lot is new to me here, I should replace "clone()" with
> :man:`clone`
> Will the same work for clone3? i.e. :man:`clone3`?

FYI man2 is for man 2 section, man 3 is for man 3 section:

doc/conf.py

    'man2': ('https://man7.org/linux/man-pages/man2/%s.2.html', '%s(2)'),
    'man3': ('https://man7.org/linux/man-pages/man3/%s.3.html', '%s(3)'),

i.e. :man2:`clone` leads to man clone(2)
https://man7.org/linux/man-pages/man2/clone.2.html

which describes both syscalls:
clone, __clone2, clone3 - create a child process

But sure man clone3(2) links also works (the same page as man clone(2)).
https://man7.org/linux/man-pages/man2/clone3.2.html

FYI (if you have time) this should generate doc

$ cd doc; make setup && make

which is under ./html/users/test_catalog.html
and online:
https://linux-test-project.readthedocs.io/en/latest/users/test_catalog.html

> I understand the other comments and will implement them, nit or not :).

Thank you!

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2025-11-18 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 18:03 [LTP] [PATCH v3] Add new tests for clone and clone3 Stephen Bertram via ltp
2025-11-12 20:11 ` Petr Vorel
2025-11-12 21:05   ` Stephen Bertram via ltp
2025-11-18 14:54     ` Petr Vorel [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=20251118145445.GA45810@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=sbertram@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.