Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3604207pxb; Sun, 31 Jan 2021 22:50:13 -0800 (PST) X-Google-Smtp-Source: ABdhPJyRSgfPRgP8kq6oiugVxSvb4uEdvXHP5UQtbtB/iucOlgVkEttlsCPspkwMDiVFKtJ/UHzk X-Received: by 2002:a17:906:5585:: with SMTP id y5mr16280991ejp.486.1612162213010; Sun, 31 Jan 2021 22:50:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612162213; cv=none; d=google.com; s=arc-20160816; b=bXppT/390Gmflx7hBbFm3Gv48Fm8SMSqfLhmMMGyR++QVQvaQM0S0OfKKYxrEtRTMd jIySMNmsBqxq1wj9QuE+ele7GLciNTDF/4n0mLK3VdK1gonKPax5/9alK3SGLL4dlnPc 59MwtQpwXjQl9V1lH5psfbWgd65xAAcis2GpEfbI5sJZYZmHd4tVow/IwN+mMihbBBk6 B6UTd3tZUMKgzzpj8XPutSBeWnbRend3NNMwMaQl7WdPzC6nW6zmaxT01U4ocoyIeFVM XuAQH2wZOE4bNFQhcewEmFUUF+Semtlzvx03iNazBlnE18MeZG9ME1YmqOyG+CAyJCJI rATA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=5mQIIlM5CFm8xeXBVRv4nhYcFaur8L2TXYtvPPpQAxw=; b=CcmxAE7a372DvkDlPd1AbiRhn1h+GVdacA23oMMc1Es47Etz4rctDjw3lgSf+i9WxM DBgPTVOCQysxOhOtpvu8vWIHFgTQPw50fHn5KLu9kiNMAq9D+76YVe2pJWp/C9Gk0ahP jY0gkBzhBkKW6Ap9rahJXxufhppCxJStLp89ZjDXiWzr8ZSVsFb3+0RRxp2QffozGzLt fqUJ/9Rw+CfvivlGMPKi4zbOnIhWB7x7rm5EbLr5gtvG0fZM71K1wIHi0La1CAK2hIPq M7F397ir6lGZ5DJmnaSKjSadV3QXlLGUo2Mu9QfcrsbWxnl9+8ENLtXj6L0SCRp+fcBG lsXA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="dhKJrP/x"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id qc23si176593ejb.467.2021.01.31.22.49.49; Sun, 31 Jan 2021 22:50:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="dhKJrP/x"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231726AbhBAGqt (ORCPT + 99 others); Mon, 1 Feb 2021 01:46:49 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:37068 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231597AbhBAFls (ORCPT ); Mon, 1 Feb 2021 00:41:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612158016; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=5mQIIlM5CFm8xeXBVRv4nhYcFaur8L2TXYtvPPpQAxw=; b=dhKJrP/xoCyPJVF3+19azybF6bXigf5S1QqUbP0OcLRkomGIkEA3LySWzpHkifxUuXWbSz rBSsQD3V/+pwLc0faEQwEoL9/26syyuQeVsDNbzTjzXQandpt9gPgc9Aa0cfsJV1Bq2qAX ZiE2kpegDo8REL30KL8gSu1fDwLa3PU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-229-vKvb8gjeOfq7lZK4FcopZQ-1; Mon, 01 Feb 2021 00:40:15 -0500 X-MC-Unique: vKvb8gjeOfq7lZK4FcopZQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BD98FCC620; Mon, 1 Feb 2021 05:40:13 +0000 (UTC) Received: from [10.72.13.120] (ovpn-13-120.pek2.redhat.com [10.72.13.120]) by smtp.corp.redhat.com (Postfix) with ESMTP id 476F627CA9; Mon, 1 Feb 2021 05:40:03 +0000 (UTC) Subject: Re: [PATCH RFC v2 03/10] vringh: reset kiov 'consumed' field in __vringh_iov() To: Stefano Garzarella , virtualization@lists.linux-foundation.org Cc: Xie Yongji , "Michael S. Tsirkin" , Laurent Vivier , Stefan Hajnoczi , linux-kernel@vger.kernel.org, Max Gurtovoy , kvm@vger.kernel.org References: <20210128144127.113245-1-sgarzare@redhat.com> <20210128144127.113245-4-sgarzare@redhat.com> From: Jason Wang Message-ID: <62bb2e93-4ac3-edf5-2baa-4c2be8257cf0@redhat.com> Date: Mon, 1 Feb 2021 13:40:01 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20210128144127.113245-4-sgarzare@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/1/28 下午10:41, Stefano Garzarella wrote: > __vringh_iov() overwrites the contents of riov and wiov, in fact it > resets the 'i' and 'used' fields, but also the consumed field should > be reset to avoid an inconsistent state. > > Signed-off-by: Stefano Garzarella I had a question(I remember we had some discussion like this but I forget the conclusion): I see e.g in vringh_getdesc_kern() it has the following comment: /*  * Note that you may need to clean up riov and wiov, even on error!  */ So it looks to me the correct way is to call vringh_kiov_cleanup() before? Thanks > --- > drivers/vhost/vringh.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/vhost/vringh.c b/drivers/vhost/vringh.c > index f68122705719..bee63d68201a 100644 > --- a/drivers/vhost/vringh.c > +++ b/drivers/vhost/vringh.c > @@ -290,9 +290,9 @@ __vringh_iov(struct vringh *vrh, u16 i, > return -EINVAL; > > if (riov) > - riov->i = riov->used = 0; > + riov->i = riov->used = riov->consumed = 0; > if (wiov) > - wiov->i = wiov->used = 0; > + wiov->i = wiov->used = wiov->consumed = 0; > > for (;;) { > void *addr;