public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v7] clone3: Add clone3's clone_args cgroup
Date: Fri, 1 Sep 2023 12:22:21 +0200	[thread overview]
Message-ID: <20230901102221.GB323151@pevik> (raw)
In-Reply-To: <20230901101954.GA323151@pevik>

> Hi Wei, Richie,

> > Hello,

> > Wei Gao via ltp <ltp@lists.linux.it> writes:

> > > +
> > > +static struct tst_test test = {
> > > +	.test_all = run,
> > > +	.setup = setup,
> > > +	.cleanup = cleanup,
> > > +	.forks_child = 1,
> > > +	.max_runtime = 20,

> > I removed this and merged!

> This change, merged as 45f6916ba ("clone3: Add clone3's clone_args cgroup")
> caused failing clone302:

> tst_buffers.c:56: TINFO: Test is using guarded buffers
> tst_test.c:1559: TINFO: Timeout per run is 0h 00m 30s
> clone302.c:101: TPASS: invalid args: clone3() failed as expected: EFAULT (14)
> clone302.c:101: TPASS: zero size: clone3() failed as expected: EINVAL (22)
> clone302.c:91: TFAIL: short size: clone3() passed unexpectedly
> clone302.c:101: TPASS: extra size: clone3() failed as expected: EFAULT (14)
> clone302.c:101: TPASS: sighand-no-VM: clone3() failed as expected: EINVAL (22)
> clone302.c:101: TPASS: thread-no-sighand: clone3() failed as expected: EINVAL (22)
> clone302.c:101: TPASS: fs-newns: clone3() failed as expected: EINVAL (22)
> clone302.c:101: TPASS: invalid pidfd: clone3() failed as expected: EFAULT (14)
> clone302.c:101: TPASS: invalid signal: clone3() failed as expected: EINVAL (22)
> clone302.c:101: TPASS: zero-stack-size: clone3() failed as expected: EINVAL (22)
> clone302.c:101: TPASS: invalid-stack: clone3() failed as expected: EINVAL (22)

FYI include/lapi/sched.h change caused the regression.

Kind regards,
Petr

> Summary:
> passed   10
> failed   1
> broken   0
> skipped  0
> warnings 0
> ### TEST clone302 COMPLETE >>> 1.

> Could you please have look and fix it?

> Kind regards,
> Petr

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

  reply	other threads:[~2023-09-01 10:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26  0:35 [LTP] [PATCH v1] clone3: Add clone3's clone_args cgroup Wei Gao via ltp
2023-03-23  9:26 ` Petr Vorel
2023-03-23 12:17   ` Wei Gao via ltp
2023-03-24  6:32     ` Petr Vorel
2023-03-24  6:54       ` Wei Gao via ltp
2023-03-24  8:26         ` Petr Vorel
2023-04-21 12:38 ` [LTP] [PATCH v2] " Wei Gao via ltp
2023-04-21 13:29   ` Cyril Hrubis
2023-04-22  1:42   ` [LTP] [PATCH v3] " Wei Gao via ltp
2023-04-26 13:44     ` Cyril Hrubis
2023-05-09  0:31     ` [LTP] [PATCH v4] " Wei Gao via ltp
2023-05-17  9:28       ` Petr Vorel
2023-05-17 12:08       ` [LTP] [PATCH v5] " Wei Gao via ltp
2023-08-25 10:36         ` Richard Palethorpe
2023-08-29 23:26           ` Wei Gao via ltp
2023-08-30  8:02             ` Richard Palethorpe
2023-08-29 23:18         ` [LTP] [PATCH v6] " Wei Gao via ltp
2023-08-31  6:47           ` [LTP] [PATCH v7] " Wei Gao via ltp
2023-08-31  9:19             ` Richard Palethorpe
2023-09-01 10:19               ` Petr Vorel
2023-09-01 10:22                 ` Petr Vorel [this message]
2023-09-02  5:05                 ` Wei Gao via ltp
2024-04-04 20:42             ` Petr Vorel

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=20230901102221.GB323151@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.de \
    /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