public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wei Gao via ltp <ltp@lists.linux.it>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4] unshare03.c: Add test coverage for dup_fd() failure handling in unshare_fd()
Date: Wed, 5 Mar 2025 21:24:11 -0500	[thread overview]
Message-ID: <Z8kHSwZscoA0fUAu@wegao> (raw)
In-Reply-To: <777ccd32-5b2c-42c8-aec5-8abaa3884751@suse.com>

On Wed, Mar 05, 2025 at 01:11:20PM +0100, Andrea Cervesato wrote:
> Hi,
> 
> On 3/5/25 08:04, Wei Gao wrote:
> > > > +	if (!SAFE_CLONE(&args)) {
> > > > +		SAFE_FILE_PRINTF(FS_NR_OPEN, "%d", nr_open);
> > > > +		TST_EXP_FAIL(unshare(CLONE_FILES), EMFILE);
> > > > +		TST_CHECKPOINT_WAKE(0);
> > > There's no need to use synchronization mechanisms because at the end of the
> > > test we call tst_reap_children() waiting for all the children to be
> > > completed.
> > There are some race condition happen and trigger failure sometimes if you do not
> > use this synchronization(Currently no idea why this happen).
> > Rerun case 30 times can trigger 2 or 3 cases failed if not use synchronization in my env.
> 
> I'm really trying to reproduce this issue, but I can't. Run the test with
> 100000 iterations and it didn't stuck. Can you please check again? I tried
> on TW.

I have retest on my local machine with following builds, issue seems not happen:
* openSUSE Leap 15.5 5.14.21-150500.53-default
* Debian 6.12.0-rc4-00047-gc2ee9f594da8-dirty

so i suppose we can merge my latest v5 patch without sync.

> 
> Andrea

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

  reply	other threads:[~2025-03-06  2:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  8:19 [LTP] [PATCH v1] unshare03.c: Add test coverage for dup_fd() failure handling in unshare_fd() Wei Gao via ltp
2025-02-19 15:12 ` Andrea Cervesato via ltp
2025-03-03  9:42 ` [LTP] [PATCH v2] " Wei Gao via ltp
2025-03-03 10:47   ` Andrea Cervesato via ltp
2025-03-04  4:03     ` Wei Gao via ltp
2025-03-04  3:43   ` [LTP] [PATCH v3] " Wei Gao via ltp
2025-03-04  4:06     ` [LTP] [PATCH v4] " Wei Gao via ltp
2025-03-04  8:31       ` Andrea Cervesato via ltp
2025-03-05  7:04         ` Wei Gao via ltp
2025-03-05 12:11           ` Andrea Cervesato via ltp
2025-03-06  2:24             ` Wei Gao via ltp [this message]
2025-03-06  2:22       ` [LTP] [PATCH v5] " Wei Gao via ltp
2025-03-06  8:23         ` Andrea Cervesato via ltp

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=Z8kHSwZscoA0fUAu@wegao \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --cc=wegao@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox