From: Cyril Hrubis <chrubis@suse.cz>
To: Sebastian Chlad <sebastianchlad@gmail.com>
Cc: Sebastian Chlad <sebastian.chlad@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v5 1/2] lapi: Add io_uring_clone_buffers and RDS_CMSG_ZCOPY_COOKIE fallbacks
Date: Wed, 10 Jun 2026 16:30:11 +0200 [thread overview]
Message-ID: <ail084ZtfQErQjuR@yuki.lan> (raw)
In-Reply-To: <20260604163909.17853-1-sebastian.chlad@suse.com>
Hi!
> --- a/include/lapi/io_uring.h
> +++ b/include/lapi/io_uring.h
> @@ -265,6 +265,23 @@ struct io_uring_probe {
>
> #endif /* IOSQE_FIXED_FILE */
>
> +/* linux/io_uring.h: IORING_REGISTER_CLONE_BUFFERS = 30 */
> +#ifndef IORING_REGISTER_CLONE_BUFFERS
> +# define IORING_REGISTER_CLONE_BUFFERS 30
> +#endif
> +
> +/* Argument for IORING_REGISTER_CLONE_BUFFERS (linux/io_uring.h) */
> +#ifndef HAVE_STRUCT_IO_URING_CLONE_BUFFERS
> +struct io_uring_clone_buffers {
> + uint32_t src_fd;
> + uint32_t flags;
> + uint32_t src_off;
> + uint32_t dst_off;
> + uint32_t nr;
> + uint32_t pad[3];
> +};
> +#endif
> +
> #ifndef IOSQE_IO_HADRLINK
> /* like LINK, but stronger */
> #define IOSQE_IO_HARDLINK_BIT 3
> diff --git a/include/lapi/rds.h b/include/lapi/rds.h
> new file mode 100644
> index 000000000..7405a7f37
> --- /dev/null
> +++ b/include/lapi/rds.h
> @@ -0,0 +1,16 @@
> +// SPDX-License-Identifier: GPL-2.0-or-later
> +/*
> + * Copyright (C) 2026 SUSE LLC Sebastian Chlad <sebastian.chlad@suse.com>
> + */
> +
> +#ifndef LAPI_RDS_H__
> +#define LAPI_RDS_H__
> +
> +#include <linux/rds.h>
> +
> +/* Fallback for older userspace headers (e.g. openSUSE Leap 42.2). */
Generally we do not add such comments that mostly state the obvious.
The less comments like this we add the better, apart from adding visual
noise they also tend to go out of sync with the code.
Please add only the fallbacks without the comments.
> +#ifndef RDS_CMSG_ZCOPY_COOKIE
> +# define RDS_CMSG_ZCOPY_COOKIE 12
> +#endif
> +
> +#endif /* LAPI_RDS_H__ */
> --
> 2.51.0
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-06-10 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 10:17 [LTP] [PATCH] io_uring/pintheft: Add CVE-2026-43494 regression test Sebastian Chlad
2026-05-23 11:19 ` [LTP] " linuxtestproject.agent
2026-05-25 9:36 ` Cyril Hrubis
2026-05-29 10:18 ` Andrea Cervesato via ltp
2026-05-29 11:56 ` Cyril Hrubis
2026-05-23 11:39 ` [LTP] [PATCH v2] " Sebastian Chlad
2026-05-23 13:30 ` [LTP] " linuxtestproject.agent
2026-05-23 15:10 ` [LTP] [PATCH v3] " Sebastian Chlad
2026-05-23 16:17 ` [LTP] " linuxtestproject.agent
2026-05-23 16:57 ` [LTP] [PATCH v4] " Sebastian Chlad
2026-05-23 18:07 ` [LTP] " linuxtestproject.agent
2026-05-24 18:16 ` [LTP] [PATCH v4] " Petr Vorel
2026-05-28 16:45 ` Martin Doucha
2026-05-28 21:31 ` Petr Vorel
2026-05-28 16:36 ` Martin Doucha
2026-06-04 16:38 ` [LTP] [PATCH v5 1/2] lapi: Add io_uring_clone_buffers and RDS_CMSG_ZCOPY_COOKIE fallbacks Sebastian Chlad
2026-06-04 16:38 ` [LTP] [PATCH v5 2/2] io_uring04: Add CVE-2026-43494 regression test Sebastian Chlad
2026-06-05 15:30 ` Martin Doucha
2026-06-10 14:52 ` Cyril Hrubis
2026-06-04 18:00 ` [LTP] lapi: Add io_uring_clone_buffers and RDS_CMSG_ZCOPY_COOKIE fallbacks linuxtestproject.agent
2026-06-10 14:30 ` Cyril Hrubis [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=ail084ZtfQErQjuR@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=sebastian.chlad@suse.com \
--cc=sebastianchlad@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.