All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC PATCH 1/1] sched: Remove process.c
Date: Mon, 13 Sep 2021 14:58:17 +0200	[thread overview]
Message-ID: <YT9K6Xl9iP8sx2/y@yuki> (raw)
Message-ID: <20210913125817._j69lBbfuKH-VkIdxWybZyd6Ru19DbJFlF8bK14mgGk@z> (raw)
In-Reply-To: <20210913100022.14501-1-pvorel@suse.cz>

Hi!
> Test was removed as buggy from the runtest file nearly 20 years ago in:
> 576f1ee56 ("Removed a test that was not correctly running.")
> 
> Test is probably obsolete, not using even legacy API, non-zero exit:
> 
> $ ./process -d 8 -b 2 -t 1; echo $?
> total number of process to be created nodesum (511) is greater
>  than the allowed SEMMSL value (250)
> reseting the value of nodesum to SEMMSL
> Terminated
> 143
> 
> + leaving very high load after being terminated.
> 
> Reported-by: Li Wang <liwang@redhat.com>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>

I was looking at the test and while the idea seems to valid and
interesting, the implementation is buggy, it does not take much to make
it segfault and it tends to leave processes unterminated, so it would be
probably easier to implement something from scratch.[

Reviewed-by: Cyril Hrubis <chrubis@suse.cz>

-- 
Cyril Hrubis
chrubis@suse.cz

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

  reply	other threads:[~2021-09-13 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 10:00 [LTP] [RFC PATCH 1/1] sched: Remove process.c Petr Vorel
2021-09-13 10:00 ` Petr Vorel
2021-09-13 12:58   ` Cyril Hrubis [this message]
2021-09-13 12:58     ` Cyril Hrubis
2021-09-14  2:27   ` Li Wang
2021-09-14  2:27     ` Li Wang
2021-09-14  4:56       ` Petr Vorel
2021-09-14  4:56         ` 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=YT9K6Xl9iP8sx2/y@yuki \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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.