Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: XiaoLei Wu <wxl18715129466@gmail.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lapi/fcntl.h: fix O_PATH fallback on alpha
Date: Tue,  2 Jun 2026 11:23:53 +0000	[thread overview]
Message-ID: <20260602112353.4005-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260602064115.718468-1-wxl18715129466@gmail.com>

Hi XiaoLei Wu,

The fix is correct — arch/alpha/include/uapi/asm/fcntl.h confirms that
alpha defines O_PATH as 040000000, while the asm-generic fallback
010000000 collides with alpha's O_CLOEXEC value, so the bug is real and
the chosen value is right.

One style issue below.

---

> diff --git a/include/lapi/fcntl.h b/include/lapi/fcntl.h
> @@ -137,6 +137,8 @@
>  #ifndef O_PATH
>  # ifdef __sparc__
>  #  define O_PATH 0x1000000
> +# elif defined(__alpha__)
> +#  define O_PATH 040000000
>  # else

The existing arm uses `# ifdef __sparc__`, but the new arm uses
`# elif defined(__alpha__)`.  Within the same #if/#elif chain the
style should be consistent.  Please use `# elif __alpha__` to match
the surrounding code:

  # ifdef __sparc__
  #  define O_PATH 0x1000000
  # elif __alpha__
  #  define O_PATH 040000000
  # else
  #  define O_PATH 010000000
  # endif

---

Commit message looks good: accurate subject, clear rationale, proper
Signed-off-by.

It would be helpful (but not required) to note in the commit body that
the generic value 010000000 maps to O_CLOEXEC on alpha, explaining why
the mismatch causes a silent semantic failure rather than an obvious
error.

Verdict: Needs revision (style fix above)

LTP AI Reviewer

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

  reply	other threads:[~2026-06-02 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  6:41 [LTP] [PATCH] lapi/fcntl.h: fix O_PATH fallback on alpha XiaoLei Wu
2026-06-02 11:23 ` linuxtestproject.agent [this message]
2026-06-03  9:52 ` Cyril Hrubis

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=20260602112353.4005-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=wxl18715129466@gmail.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