netdev - [PATCH net-next v4 0/3] vsock: Introduce SIOCINQ ioctl support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250630075411.209928-1-niuxuewei.nxw@antgroup.com>
Date: Mon, 30 Jun 2025 15:54:11 +0800
From: Xuewei Niu <niuxuewei97@...il.com>
To: sgarzare@...hat.com
Cc: davem@...emloft.net,
	decui@...rosoft.com,
	fupan.lfp@...group.com,
	jasowang@...hat.com,
	kvm@...r.kernel.org,
	leonardi@...hat.com,
	linux-kernel@...r.kernel.org,
	mst@...hat.com,
	netdev@...r.kernel.org,
	niuxuewei.nxw@...group.com,
	niuxuewei97@...il.com,
	pabeni@...hat.com,
	stefanha@...hat.com,
	virtualization@...ts.linux.dev,
	xuanzhuo@...ux.alibaba.com
Subject: [PATCH net-next v4 0/3] vsock: Introduce SIOCINQ ioctl support

> On Mon, Jun 30, 2025 at 03:38:24PM +0800, Xuewei Niu wrote:
> >Introduce SIOCINQ ioctl support for vsock, indicating the length of unread
> >bytes.
> 
> I think something went wrong with this version of the series, because I 
> don't see the patch introducing support for SIOCINQ ioctl in af_vsock.c, 
> or did I miss something?

Oh yes. Since adding a patch for hyper-v, I forgot to update the `git
format-patch` command...

Please ignore this patchset and I'll resend a new one.

Thanks,
Xuewei

> >Similar with SIOCOUTQ ioctl, the information is transport-dependent.
> >
> >The first patch adds SIOCINQ ioctl support in AF_VSOCK.
> >
> >Thanks to @dexuan, the second patch is to fix the issue where hyper-v
> >`hvs_stream_has_data()` doesn't return the readable bytes.
> >
> >The third patch wraps the ioctl into `ioctl_int()`, which implements a
> >retry mechanism to prevent immediate failure.
> >
> >The last one adds two test cases to check the functionality. The changes
> >have been tested, and the results are as expected.
> >
> >Signed-off-by: Xuewei Niu <niuxuewei.nxw@...group.com>
> >
> >--
> >
> >v1->v2:
> >https://lore.kernel.org/lkml/20250519070649.3063874-1-niuxuewei.nxw@antgroup.com/
> >- Use net-next tree.
> >- Reuse `rx_bytes` to count unread bytes.
> >- Wrap ioctl syscall with an int pointer argument to implement a retry
> >  mechanism.
> >
> >v2->v3:
> >https://lore.kernel.org/netdev/20250613031152.1076725-1-niuxuewei.nxw@antgroup.com/
> >- Update commit messages following the guidelines
> >- Remove `unread_bytes` callback and reuse `vsock_stream_has_data()`
> >- Move the tests to the end of array
> >- Split the refactoring patch
> >- Include <sys/ioctl.h> in the util.c
> >
> >v3->v4:
> >https://lore.kernel.org/netdev/20250617045347.1233128-1-niuxuewei.nxw@antgroup.com/
> >- Hyper-v `hvs_stream_has_data()` returns the readable bytes
> >- Skip testing the null value for `actual` (int pointer)
> >- Rename `ioctl_int()` to `vsock_ioctl_int()`
> >- Fix a typo and a format issue in comments
> >- Remove the `RECEIVED` barrier.
> >- The return type of `vsock_ioctl_int()` has been changed to bool
> >
> >Xuewei Niu (3):
> >  hv_sock: Return the readable bytes in hvs_stream_has_data()
> >  test/vsock: Add retry mechanism to ioctl wrapper
> >  test/vsock: Add ioctl SIOCINQ tests
> >
> > net/vmw_vsock/hyperv_transport.c | 16 +++++--
> > tools/testing/vsock/util.c       | 32 +++++++++----
> > tools/testing/vsock/util.h       |  1 +
> > tools/testing/vsock/vsock_test.c | 80 ++++++++++++++++++++++++++++++++
> > 4 files changed, 117 insertions(+), 12 deletions(-)
> >
> >-- 
> >2.34.1
> >