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 A1903A0A05 for ; Tue, 19 Jan 2021 13:15:20 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8F9DE140DE2; Tue, 19 Jan 2021 13:15:20 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mails.dpdk.org (Postfix) with ESMTP id 16B65140DE2 for ; Tue, 19 Jan 2021 13:15:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1611058518; 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: in-reply-to:in-reply-to:references:references; bh=gzlJit17T5408bXEEd9rtduQZRdmDiUX7AqILn0Tbeo=; b=G4yc3kvuJ8fjUy1BKz7jy9YO00gly/cGaGx5yY85iudeHqImsPVIAzlOw9oQLy3tm68Naj Zuy5ai18RK43lXSlvzTxgsn8yVByTIgPri6D4j9xTO1Iu6rlJQ2b9eiHfaH8h3Ag9rNYMJ R23WriHCcqNHJj1sqLrDYtX6F52gKuQ= Received: from mail-vk1-f200.google.com (mail-vk1-f200.google.com [209.85.221.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-298-obLzdoWBO-yt2Kf7SLNCkA-1; Tue, 19 Jan 2021 07:15:17 -0500 X-MC-Unique: obLzdoWBO-yt2Kf7SLNCkA-1 Received: by mail-vk1-f200.google.com with SMTP id s127so10552521vka.11 for ; Tue, 19 Jan 2021 04:15:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gzlJit17T5408bXEEd9rtduQZRdmDiUX7AqILn0Tbeo=; b=K75ilTbNEcJ3bTm4yGkYRKcmnpMKcAf9nPAoQLqJEG831g4u+M8OjYEJeC2AiNIO6W am3P2/UpX0cKk9M03h2tWR2wJ3M0nh9ImJEy+zyazAuDjmmMhtP0Eyq6GHSiRCAZ0G+k qNA9YzvkaYjnTl3cp3zFee/S/mP+3N4UN2fTgiglnkaIfbQ1htTTkBPr2hGo3RwG7OrL uSYrTVKNcKCpMwEptxO9pv53EydNpVH5Kqnz9F1AwywJjgroihASJfFinWkZuZf1cZ5B PNUBiS+hnd0UO9rAbETf1WfPmtcu06GE5hXcEfqoNsCgtGZh0WXTjnS/qZH6mrjHJVYL vBrg== X-Gm-Message-State: AOAM530hpdkZKhR/Fia5FyxB4gh97o3Vnl26G+KI7KSmCY8sd1+mGAVQ V16PhETV/JyisSsyQmfp0aqUc5ZInBNwqC0CgvXXttxdmJbM5Qom07axUtQWNepZr4HRZRPuE4b xG959FXpXIyS/9lH2aGIfCik= X-Received: by 2002:a67:3093:: with SMTP id w141mr2395082vsw.27.1611058515893; Tue, 19 Jan 2021 04:15:15 -0800 (PST) X-Google-Smtp-Source: ABdhPJzLAF3XbJZJgbnGFTScnVArAPcfzsjz29z1QkUuHpFDIPGc/JkAPCwsZMjSG3EKkeKGZWTLIhOjMGp8RiT9Ino= X-Received: by 2002:a67:3093:: with SMTP id w141mr2395076vsw.27.1611058515640; Tue, 19 Jan 2021 04:15:15 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Tue, 19 Jan 2021 13:15:04 +0100 Message-ID: To: Anatoly Burakov Cc: dev , dpdk stable Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] fbarray: fix incorrect overlap check X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On Thu, Jan 14, 2021 at 4:03 PM Anatoly Burakov wrote: > > When we're attaching fbarrays in secondary processes, we check for > whether the intended memory address for the fbarray is already in use by > some other, local fbarray. However, the check for end-overlap (i.e. to > see if our memory area's end overlaps with some other fbarray) is > incorrectly counting end offset as part of the overlap. Fix the check. > > Fixes: 5b61c62cfd76 ("fbarray: add internal tailq for mapped areas") > Cc: stable@dpdk.org > > Signed-off-by: Anatoly Burakov Tested-by: Zhihong Peng Applied. -- David Marchand