From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 121DF41EB1; Thu, 16 Mar 2023 15:47:41 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0290B42D4B; Thu, 16 Mar 2023 15:47:41 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 1B89442D4B for ; Thu, 16 Mar 2023 15:47:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678978058; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TMthQ1ZFslXNCqr0e8iyTySUlGeiTx7qZZ++ZSnbyss=; b=BF2vFDwfW8BsmiRaJIA8Kt2CYB/Z32AnrIIvGmFQ0EG7xsRqcPOk89+QWswm+y4EWwAN2B fhhZz8lsvlqPXjiQ/i1fBH7cO6vhcyag7PsjYMWqh4GLh7YgBYk9nRFii7hiwBdAh0xMZG +m12TCwmi5iUieZ3FbAoDqMQSaeRx8I= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-340-hVvB_ctGMoeoC7NzPCZ9ng-1; Thu, 16 Mar 2023 10:47:36 -0400 X-MC-Unique: hVvB_ctGMoeoC7NzPCZ9ng-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id BE55F96DC87; Thu, 16 Mar 2023 14:47:35 +0000 (UTC) Received: from [10.39.208.23] (unknown [10.39.208.23]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DDE462166B26; Thu, 16 Mar 2023 14:47:34 +0000 (UTC) Message-ID: <4f1d3d7e-da4a-4fba-9bfb-865e4ca60c9c@redhat.com> Date: Thu, 16 Mar 2023 15:47:33 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH] vhost: fix possible null pointer dereference To: dev@dpdk.org, mkp@redhat.com, chenbo.xia@intel.com, david.marchand@redhat.com References: <20230309113631.300351-1-maxime.coquelin@redhat.com> From: Maxime Coquelin In-Reply-To: <20230309113631.300351-1-maxime.coquelin@redhat.com> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On 3/9/23 12:36, Maxime Coquelin wrote: > When handling VHOST_USER_SET_MEM_TABLE request ending > up in changing existing memory map, a device's memory > pointer may ends up being dereference while being NULL in > IOTLB cache flush function. > > Coverity issue: 383646 > Fixes: dea092d0addb ("vhost: fix madvise arguments alignment") > > Signed-off-by: Maxime Coquelin > --- > lib/vhost/vhost_user.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) > Applied to dpdk-next-virtio/main. Thanks, Maxime