Messages in this thread | | | From | Sunil Muthuswamy <> | Subject | RE: [PATCH] hv_sock: Fix data loss upon socket close | Date | Tue, 14 May 2019 16:33:31 +0000 |
| |
> -----Original Message----- > From: linux-hyperv-owner@vger.kernel.org <linux-hyperv-owner@vger.kernel.org> On Behalf Of David Miller > Sent: Thursday, May 9, 2019 1:58 PM > To: Sunil Muthuswamy <sunilmut@microsoft.com> > Cc: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang <haiyangz@microsoft.com>; Stephen Hemminger > <sthemmin@microsoft.com>; sashal@kernel.org; Dexuan Cui <decui@microsoft.com>; Michael Kelley <mikelley@microsoft.com>; > netdev@vger.kernel.org; linux-hyperv@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] hv_sock: Fix data loss upon socket close > > From: Sunil Muthuswamy <sunilmut@microsoft.com> > Date: Wed, 8 May 2019 23:10:35 +0000 > > > +static inline void hvs_shutdown_lock_held(struct hvsock *hvs, int mode) > > Please do not use the inline keyword in foo.c files, let the compiler decide. > Thanks, will fix in the next version. > Also, longer term thing, I notice that vsock_remove_socket() is very > inefficient locking-wise. It takes the table lock to do the placement > test, and takes it again to do the removal. Might even be racy. Agreed. The check & remove should be done as an atomic operation. This can be taken up as a separate patch.
| |