Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp3569728ybi; Sun, 2 Jun 2019 18:05:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqzyoWvqr0LQmhyOfV9M11E6mJ2LaIrV6LBnLT7swhvxf9nZmZTCAQmWjUGsgIW3Z1YwfaFC X-Received: by 2002:a17:902:1029:: with SMTP id b38mr26270682pla.72.1559523905193; Sun, 02 Jun 2019 18:05:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559523905; cv=none; d=google.com; s=arc-20160816; b=Pt23K3yzV2NJIhrkUoQUSTHA2HI6FeUsyp2idYr2IRgKX8yozNUe14II9vHuH+//6P +NZcvntLcFFNZTZ0qdXw0OvCi3vjm7fK57GV4EiOCxv4GNnWS6KCO6gzQXe6dtKcrL2/ 7ErH+sFvFA5TgbhImEfUgueKjkoxCazUh6WUMewkqxs1mSFO7+omJwc7hfA3gP04NTxl 9SZdhJ40JeN7eRvgZnvbm2Vv5fGsfGK/VSuuYzDgi5obFgeHrqlyeHykivnBy8EsBI07 upnEi+A2bFKlo+fOKQyRH2m8+G0cEIlY1R0zqdQnwZ8690mvMn135Gj/rItqE/dKnV+z vHjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=K1OQ73R2PHmxbHpcRhVHQynsd+38L1klZKq9f9qwxBs=; b=SzUPpwFCtauTp3Yta7YRf5U81vHb062rIha+6S6iOvn5TmwDdcZHb4FGO7rNDrlUfU c/xi3vlb78vs8TDYtNxKw/6ECs92eREfVcNI3Q3tsyYRCPt7UJSnFZF4/EXkILaSijnt KxGDfWAulCGNwH5QT16OIT4JEl9U2dw5dNvU0iaUjKB49aF7oiSKNxWXBdbDzDhbnK/n fe10r6M8+qLDuZ/6Tf0hx+I/KiFhMs21wmky/MZ9agxkpxfcZtmK75V+Ew9RoQcwpnl6 INeWj8dx/gKZFcursJVLXK9eNMkzW24BqJCB0s1XlRGi3OdazR1fp71VMDR/a5Tm2FBv 6bkQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d197si15234470pga.110.2019.06.02.18.04.47; Sun, 02 Jun 2019 18:05:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726840AbfFCBDg (ORCPT + 99 others); Sun, 2 Jun 2019 21:03:36 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:50546 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726270AbfFCBDg (ORCPT ); Sun, 2 Jun 2019 21:03:36 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::3d5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 2F5E113407F4E; Sun, 2 Jun 2019 18:03:35 -0700 (PDT) Date: Sun, 02 Jun 2019 18:03:34 -0700 (PDT) Message-Id: <20190602.180334.1932703293092139564.davem@davemloft.net> To: sgarzare@redhat.com Cc: netdev@vger.kernel.org, stefanha@redhat.com, virtualization@lists.linux-foundation.org, mst@redhat.com, jasowang@redhat.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [PATCH v3 2/5] vsock/virtio: fix locking for fwd_cnt and buf_alloc From: David Miller In-Reply-To: <20190531133954.122567-3-sgarzare@redhat.com> References: <20190531133954.122567-1-sgarzare@redhat.com> <20190531133954.122567-3-sgarzare@redhat.com> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Sun, 02 Jun 2019 18:03:35 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Stefano Garzarella Date: Fri, 31 May 2019 15:39:51 +0200 > @@ -434,7 +434,9 @@ void virtio_transport_set_buffer_size(struct vsock_sock *vsk, u64 val) > if (val > vvs->buf_size_max) > vvs->buf_size_max = val; > vvs->buf_size = val; > + spin_lock_bh(&vvs->rx_lock); > vvs->buf_alloc = val; > + spin_unlock_bh(&vvs->rx_lock); This locking doesn't do anything other than to strongly order the buf_size store to occur before the buf_alloc one. If you need a memory barrier, use one.