From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
virtualization@lists.linux.dev
Subject: [PATCH 07/14] tools/virtio: add ucopysize.h stub
Date: Thu, 4 Dec 2025 13:46:15 -0500 [thread overview]
Message-ID: <5046df90002bb744609248404b81d33b559fe813.1764873799.git.mst@redhat.com> (raw)
In-Reply-To: <cover.1764873799.git.mst@redhat.com>
Add ucopysize.h with stub implementations of check_object_size,
copy_overflow, and check_copy_size.
Created using Cursor CLI.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
tools/virtio/linux/ucopysize.h | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 tools/virtio/linux/ucopysize.h
diff --git a/tools/virtio/linux/ucopysize.h b/tools/virtio/linux/ucopysize.h
new file mode 100644
index 000000000000..8beb7755d060
--- /dev/null
+++ b/tools/virtio/linux/ucopysize.h
@@ -0,0 +1,21 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+#ifndef __LINUX_UCOPYSIZE_H__
+#define __LINUX_UCOPYSIZE_H__
+
+#include <linux/bug.h>
+
+static inline void check_object_size(const void *ptr, unsigned long n,
+ bool to_user)
+{ }
+
+static inline void copy_overflow(int size, unsigned long count)
+{
+}
+
+static __always_inline __must_check bool
+check_copy_size(const void *addr, size_t bytes, bool is_source)
+{
+ return true;
+}
+
+#endif /* __LINUX_UCOPYSIZE_H__ */
--
MST
next prev parent reply other threads:[~2025-12-04 18:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 18:45 [PATCH 00/14] tools/virtio: cleanups, fixes Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 01/14] tools/virtio: fix up compiler.h stub Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 02/14] virtio: make it self-contained Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 03/14] tools/virtio: use kernel's virtio.h Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 04/14] tools/virtio: add struct module forward declaration Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 05/14] tools/virtio: stub DMA mapping functions Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 06/14] tools/virtio: add dev_WARN_ONCE and is_vmalloc_addr stubs Michael S. Tsirkin
2025-12-04 18:46 ` Michael S. Tsirkin [this message]
2025-12-04 18:46 ` [PATCH 08/14] tools/virtio: pass KCFLAGS to module build Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 09/14] tools/virtio: add struct cpumask to cpumask.h Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 10/14] tools/virtio: stub might_sleep and synchronize_rcu Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 11/14] tools/virtio: switch to kernel's virtio_config.h Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 12/14] virtio_features: make it self-contained Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 13/14] tools/virtio: fix up oot build Michael S. Tsirkin
2025-12-04 18:46 ` [PATCH 14/14] tools/virtio: add device, device_driver stubs Michael S. Tsirkin
2025-12-09 13:09 ` [PATCH 00/14] tools/virtio: cleanups, fixes Michael S. Tsirkin
2025-12-10 6:24 ` Jason Wang
2025-12-10 7:01 ` Michael S. Tsirkin
2025-12-11 7:12 ` Michael S. Tsirkin
2025-12-11 7:22 ` Jason Wang
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=5046df90002bb744609248404b81d33b559fe813.1764873799.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®