Linux Test Project
 help / color / mirror / Atom feed
From: Li Wang <li.wang@linux.dev>
To: linuxtestproject.agent@gmail.com
Cc: Wake Liu <wakel@google.com>, ltp@lists.linux.it
Subject: Re: [LTP] lib: Use backoff polling to wait for loop device nodes
Date: Mon, 10 Aug 2026 11:55:58 +0800	[thread overview]
Message-ID: <anlLyuZW-8dHISLB@linux.dev> (raw)
In-Reply-To: <20260808013246.12398-1-linuxtestproject.agent@gmail.com>

Hi Wake,

On Sat, Aug 08, 2026 at 01:32:46AM +0000, linuxtestproject.agent@gmail.com wrote:
> Hi Wake,
> 
> On Fri, 7 Aug 2026, Wake Liu wrote:
> > lib: Use backoff polling to wait for loop device nodes
> 
> > +				path_set = TST_RETRY_FN_EXP_BACKOFF(
> > +					set_dev_loop_path(rc, path, path_len),
> > +					TST_RETVAL_EQ0, 1);
> 
> Could the backoff arithmetic be made overflow-safe before these two new
> uses?
> 
> LTP_TIMEOUT_MUL=3000 is accepted by parse_mul(), which makes

Theoretically, this is correct, but I don't think anyone will
need a timeout as large as 3000 * 30s for one of LTP test.
It would take nearly 25 hours to trigger, which is unrealistic.

IOW, your patch v6 is good enough. Sometimes AI agent is too strict.

-- 
Regards,
Li Wang

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

  reply	other threads:[~2026-08-10  3:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 15:27 [LTP] [PATCH] lib: Use exponential-backoff polling to wait for loop device nodes Wake Liu via ltp
2026-08-03 16:28 ` [LTP] " linuxtestproject.agent
2026-08-04  1:59 ` [LTP] [PATCH v2] lib: Use backoff " Wake Liu via ltp
2026-08-04  3:58   ` Li Wang
2026-08-04 15:24     ` [LTP] [PATCH v3] " Wake Liu via ltp
2026-08-05  2:24       ` Li Wang
2026-08-05  2:54         ` [LTP] [PATCH v4] " Wake Liu via ltp
2026-08-05  4:09           ` [LTP] " linuxtestproject.agent
2026-08-05  6:53             ` Li Wang
2026-08-05  6:35           ` [LTP] [PATCH v4] " Li Wang
2026-08-05  6:52           ` Andrea Cervesato via ltp
2026-08-05  6:55           ` Andrea Cervesato via ltp
2026-08-05  7:10             ` Li Wang
2026-08-07 10:04               ` [LTP] [PATCH v5] " Wake Liu via ltp
2026-08-07 11:05                 ` [LTP] " linuxtestproject.agent
2026-08-07 23:49                   ` [LTP] [PATCH v6] " Wake Liu via ltp
2026-08-08  1:32                     ` [LTP] " linuxtestproject.agent
2026-08-10  3:55                       ` Li Wang [this message]
2026-08-10  4:16                         ` Wake Liu via ltp
2026-08-10  2:58                     ` [LTP] [PATCH v7 0/2] Fix overflow and use backoff polling for loop devices Wake Liu via ltp
2026-08-10  2:58                       ` [LTP] [PATCH v7 1/2] lib: Fix overflow in backoff polling and timeout multiplication Wake Liu via ltp
2026-08-10  3:56                         ` [LTP] " linuxtestproject.agent
2026-08-10  9:17                         ` [LTP] [PATCH v7 1/2] " Andrea Cervesato via ltp
2026-08-10 10:02                         ` Li Wang
2026-08-10  2:58                       ` [LTP] [PATCH v7 2/2] lib: Use backoff polling to wait for loop device nodes Wake Liu via ltp
2026-08-10  9:17                         ` Andrea Cervesato via ltp
2026-08-10 10:10                     ` [LTP] [PATCH v6] " Li Wang
2026-08-10 12:30                       ` Wake Liu 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=anlLyuZW-8dHISLB@linux.dev \
    --to=li.wang@linux.dev \
    --cc=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=wakel@google.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