From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it, "Ricardo B. Marlière" <rbm@suse.com>
Subject: Re: [LTP] [PATCH v2] Add test case to cover the setting resource limit64 for process
Date: Thu, 20 Feb 2025 10:35:00 +0100 [thread overview]
Message-ID: <20250220093500.GA2654481@pevik> (raw)
In-Reply-To: <CAEemH2fOu4FeMMEQmVWDi+tSQEVzPK0-b8-yZONt137ix8Ttkw@mail.gmail.com>
Hi Li, Chunfu Wen,
...
> > > +static int setrlimit_u64(int resource, const struct rlimit64 *rlim)
> > > +{
> > > + return tst_syscall(__NR_prlimit64, 0, resource, rlim, NULL);
> > I suppose using raw syscall is really needed, right?
> Yes, using the raw syscall for prlimit64 is necessary in this case.
> From what I know, Chufu is working oin an environment where glibc's
> wrapper might interfere, using tst_syscall(__NR_prlimit64, ...) ensures
> that the raw syscall is executed without relying on glibc behavior.
Li, thanks for info.
> @chuwen, this new case is quite similar to setrlimit06.c, maybe we
> can combine into one and use .test_variants to traverse all syscalls.
> e.g. syscalls/stime/stime_var.h.
+1
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-02-20 9:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 2:31 [LTP] [PATCH] Add test case to cover the setting resource limit64 for process chunfuwen
2025-02-18 11:44 ` Ricardo B. Marlière
2025-02-18 13:29 ` Andrea Cervesato via ltp
2025-02-19 2:35 ` Chunfu Wen
2025-02-19 9:29 ` Andrea Cervesato via ltp
2025-02-19 6:47 ` [LTP] [PATCH v2] " chunfuwen
2025-02-19 16:44 ` Petr Vorel
2025-02-20 2:08 ` Li Wang
2025-02-20 9:35 ` Petr Vorel [this message]
2025-02-20 8:01 ` Chunfu Wen
2025-02-20 8:35 ` [LTP] [PATCH v3] " Chunfu Wen
2025-02-21 10:34 ` Andrea Cervesato via ltp
2025-02-24 3:06 ` Chunfu Wen
2025-02-24 3:07 ` [LTP] [PATCH v4] " Chunfu Wen
2025-02-26 1:15 ` Chunfu Wen
2025-02-28 3:41 ` Li Wang
2025-02-28 7:45 ` Andrea Cervesato via ltp
2025-02-28 8:39 ` Li Wang
2025-02-28 9:22 ` Li Wang
2025-02-28 11:37 ` Petr Vorel
2025-02-26 9:21 ` Li Wang
2025-02-19 16:50 ` [LTP] [PATCH v2] " 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=20250220093500.GA2654481@pevik \
--to=pvorel@suse.cz \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=rbm@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