From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] Add logical_block_metadata_cap struct fallback
Date: Wed, 6 May 2026 12:58:37 +0000 [thread overview]
Message-ID: <20260506125837.4020-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260325-ioctl_getlbmd01-v1-1-00dc526e326f@suse.com>
Hi Andrea,
--- [PATCH 1/2] ---
On Wed, 25 Mar 2026 15:19:10 +0100, Andrea Cervesato wrote:
> Add logical_block_metadata_cap struct fallback
>
> Add UAPI fallback definitions for struct logical_block_metadata_cap,
> FS_IOC_GETLBMD_CAP ioctl and related LBMD_* constants in lapi/fs.h
The commit message claims LBMD_* constants are added, but none appear in
the diff. The kernel's uapi/linux/fs.h defines LBMD_PI_CAP_INTEGRITY,
LBMD_PI_CAP_REFTAG, LBMD_PI_CSUM_{NONE,IP,CRC16_T10DIF,CRC64_NVME}, and
LBMD_SIZE_VER0 — either add them to lapi/fs.h or drop the claim from the
commit message.
---
Note:
Our agent completed the review of the patch. The full review can be
found at: <not available>
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
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-05-06 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 14:19 [LTP] [PATCH 0/2] New test for ioctl(FS_IOC_GETLBMD_CAP) feature Andrea Cervesato
2026-03-25 14:19 ` [LTP] [PATCH 1/2] Add logical_block_metadata_cap struct fallback Andrea Cervesato
2026-04-27 8:25 ` Petr Vorel
2026-05-06 12:58 ` linuxtestproject.agent [this message]
2026-05-06 13:10 ` Andrea Cervesato via ltp
2026-03-25 14:19 ` [LTP] [PATCH 2/2] Add new test ioctl_getlbmd01 Andrea Cervesato
2026-04-27 8:22 ` 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=20260506125837.4020-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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