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 v2] unshare03.c: Add test coverage for dup_fd() failure handling in unshare_fd()
Date: Mon, 3 Mar 2025 23:03:22 -0500	[thread overview]
Message-ID: <Z8Z7imFU4KAW46rr@wegao> (raw)
In-Reply-To: <5a4dc2a7-dbfd-4927-ad85-7c3e0d8a00ee@suse.com>

On Mon, Mar 03, 2025 at 11:47:34AM +0100, Andrea Cervesato wrote:
> Hi!
> 
> > +
> > +	SAFE_FILE_SCANF(FS_NR_OPEN, "%d", &nr_open);
> Here we can print the number of open file descriptors, using tst_res(), to
> help debugging.
> > +
> > +	SAFE_FILE_PRINTF(FS_NR_OPEN, "%d", nr_open + 1024);
> 
> In the previous version I made a mistake in the review. The original test is
> using /proc/sys/fs/nr_open to set limits first, then it reads back them from
> the same file in order to have a starting limit. This is probably needed due
> to the kernel configurations. So please bring back the
> SAFE_GETRLIMIT(RLIMIT_NOFILE, &rlimit); line I asked to remove. Sorry for
> that.
> 
> Also, if we are going to use new increments, we need to update the next
> increments as well according to the previous ones. So feel free to leave it
> as it was before.
> 
> I must have been distracted that day :-)
No problem at all :)
I have sent new patch, feedback me if any misunderstanding.
> 
> 
> The rest looks ok.
> 
> Andrea
> 

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

  reply	other threads:[~2025-03-04  4:03 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 [this message]
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
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=Z8Z7imFU4KAW46rr@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