Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] min_free_kbytes: TCONF on errno ENOMEM, add break
Date: Mon, 25 May 2026 10:08:10 +0000	[thread overview]
Message-ID: <20260525100811.3803-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260525073921.172426-1-pvorel@suse.cz>

Hi Petr,

On Mon, 25 May 2026 09:39:21 +0200, Petr Vorel wrote:
> min_free_kbytes: TCONF on errno ENOMEM, add break
>
> On machine with 16 GM RAM and ~6 GB swap fork() fails on ENOMEM.

Typo: "GM" → "GB".

> -                       tst_brk(TBROK | TERRNO, "fork");
> +                       tst_brk((errno == ENOMEM ? TCONF : TBROK) | TERRNO, "fork");
> +                       break;

The TCONF handling is correct. Note that `tst_brk()` is `__attribute__((noreturn))`, so the `break` is unreachable. It's still fine to add for static-analysis tools and readability, but the commit message calling it a "missing" break is a stretch — it was never functionally absent.

[...]

---
Note:

Our agent completed the review of the patch. The full review can be
found at: https://github.com/linux-test-project/ltp/actions

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

---

**Verdict: Needs revision** — fix the "GM" → "GB" typo in the commit body. The code change itself is correct.

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

      parent reply	other threads:[~2026-05-25 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25  7:39 [LTP] [PATCH 1/1] min_free_kbytes: TCONF on errno ENOMEM, add break Petr Vorel
2026-05-25  9:02 ` Cyril Hrubis
2026-05-25  9:42   ` Petr Vorel
2026-05-25 11:15     ` Cyril Hrubis
2026-05-25 11:36       ` Petr Vorel
2026-05-25 10:08 ` linuxtestproject.agent [this message]

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=20260525100811.3803-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox