Re: [RESEND PATCH net-next 6/6] selftests: net: extend SCM_PIDFD test to cover stale pidfds

On Tue, Jul 1, 2025 at 9:59 AM Christian Brauner wrote: > > On Sun, Jun 29, 2025 at 11:44:43PM +0200, Alexander Mikhalitsyn wrote: > > Extend SCM_PIDFD test scenarios to also cover dead task's > > pidfd retrieval and reading its exit info. > > > > Cc: linux-kselft...@vger.kernel.org > > Cc: linux-

Re: [PATCH v2] vhost/vsock: specify module version

On Mon, Sep 30, 2024 at 5:43 PM Stefano Garzarella wrote: > > Hi Aleksandr, > > On Mon, Sep 30, 2024 at 04:43:36PM GMT, Aleksandr Mikhalitsyn wrote: > >On Mon, Sep 30, 2024 at 4:27 PM Stefano Garzarella > > wrote: > >> > >> On Sun, Sep 29, 2024 at 0

Re: [PATCH v2] vhost/vsock: specify module version

On Mon, Sep 30, 2024 at 4:27 PM Stefano Garzarella wrote: > > On Sun, Sep 29, 2024 at 08:21:03PM GMT, Alexander Mikhalitsyn wrote: > >Add an explicit MODULE_VERSION("0.0.1") specification for the vhost_vsock > >module. > > > >It is useful because it allows userspace to check if vhost_vsock is the

Re: [PATCH v2] vhost/vsock: specify module version

On Mon, Sep 30, 2024 at 4:05 PM Michael S. Tsirkin wrote: > > On Mon, Sep 30, 2024 at 02:28:30PM +0200, Aleksandr Mikhalitsyn wrote: > > On Sun, Sep 29, 2024 at 9:03 PM Michael S. Tsirkin wrote: > > > > > > On Sun, Sep 29, 2024 at 08:21:03PM +0200, Alexander Mik

Re: [PATCH v2] vhost/vsock: specify module version

On Sun, Sep 29, 2024 at 9:03 PM Michael S. Tsirkin wrote: > > On Sun, Sep 29, 2024 at 08:21:03PM +0200, Alexander Mikhalitsyn wrote: > > Add an explicit MODULE_VERSION("0.0.1") specification for the vhost_vsock > > module. > > > > It is useful because it allows userspace to check if vhost_vsock i

Re: [PATCH] vhost/vsock: specify module version

On Sun, Sep 29, 2024 at 7:48 PM Michael S. Tsirkin wrote: > > On Sun, Sep 29, 2024 at 07:35:35PM +0200, Aleksandr Mikhalitsyn wrote: > > On Sun, Sep 29, 2024 at 6:56 PM Michael S. Tsirkin wrote: > > > > > > On Thu, Sep 26, 2024 at 06:16:40PM +0200, Alexander Mik

Re: [PATCH] vhost/vsock: specify module version

On Sun, Sep 29, 2024 at 6:56 PM Michael S. Tsirkin wrote: > > On Thu, Sep 26, 2024 at 06:16:40PM +0200, Alexander Mikhalitsyn wrote: > > Add an explicit MODULE_VERSION("0.0.1") specification > > for a vhost_vsock module. It is useful because it allows > > userspace to check if vhost_vsock is there

Re: [PATCH net-next v3 2/2] ipvs: allow some sysctls in non-init user namespaces

On Fri, May 3, 2024 at 3:06 PM Julian Anastasov wrote:> > > Hello, > > On Thu, 18 Apr 2024, Alexander Mikhalitsyn wrote: > > > Let's make all IPVS sysctls writtable even when > > network namespace is owned by non-initial user namespace. > > > > Let's make a few sysctls to be read-only for

Re: [PATCH net-next v3 1/2] ipvs: add READ_ONCE barrier for ipvs->sysctl_amemthresh

On Sun, Apr 21, 2024 at 1:06 PM Julian Anastasov wrote: > > > Hello, Dear Julian, Thanks a lot for the fast review and suggestions! Kind regards, Alex > > On Thu, 18 Apr 2024, Alexander Mikhalitsyn wrote: > > > Cc: Julian Anastasov > > Cc: Simon Horman > > Cc: Pablo Neira Ayuso > >

Re: [PATCH net-next v2 1/2] ipvs: add READ_ONCE barrier for ipvs->sysctl_amemthresh

On Thu, Apr 18, 2024 at 3:23 PM Julian Anastasov wrote: > > > Hello, Dear Julian, > > On Thu, 18 Apr 2024, Alexander Mikhalitsyn wrote: > > > Cc: Julian Anastasov > > Cc: Simon Horman > > Cc: Pablo Neira Ayuso > > Cc: Jozsef Kadlecsik > > Cc: Florian Westphal > > Suggested-by: Julia

Re: [PATCH net-next] ipvs: allow some sysctls in non-init user namespaces

On Wed, Apr 17, 2024 at 3:02 PM Julian Anastasov wrote: > > > Hello, Dear Julian, > > On Tue, 16 Apr 2024, Alexander Mikhalitsyn wrote: > > > Let's make all IPVS sysctls visible and RO even when > > network namespace is owned by non-initial user namespace. > > > > Let's make a few sysctl