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 EDB8DA0505 for ; Thu, 7 Apr 2022 17:32:51 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D51C3410EF; Thu, 7 Apr 2022 17:32:51 +0200 (CEST) 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 69B5B410E3 for ; Thu, 7 Apr 2022 17:32:50 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1649345569; 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=ROGag/Uni9Rd+MWCSBcCNSAVbPss9Peg0R3v1m//rMs=; b=SDMTUzWF8JluqiKN8IjkYg5EM/9PUag/4T/x0p4rEfhNcI+qyWVCclTtXsu5Ffyb8vIjTp xnlMBP8tTLPvD9q+DeB++VfSvZRJHKRXaLyp7mcw6r41cE+FHsXVAKTW0kurdLgDuIxVkf Fke3jkIokg0XRuc5QhNr6c+P8tC+5D4= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-344-xzR07QVrNpCSAQCrVbV4YQ-1; Thu, 07 Apr 2022 11:32:46 -0400 X-MC-Unique: xzR07QVrNpCSAQCrVbV4YQ-1 Received: by mail-lj1-f200.google.com with SMTP id q5-20020a2e9145000000b002497bf0eaa1so2269165ljg.5 for ; Thu, 07 Apr 2022 08:32:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ROGag/Uni9Rd+MWCSBcCNSAVbPss9Peg0R3v1m//rMs=; b=27bJ9xQECYN95JR/XXgbFn3uMP4Uv0YSy8l7wlxGW6l05UDBKiltToqYcfE/1m6nDW fVTV1okEB41e/7M4V54jdSFyUdqQSXlrr4+GJSISWtea6qpBAQenyTbmdjy0eLp8fIHM aUpxwJ14LXE/CkvIlXQS/XczN3fnrNU8SyvbDOuvCqF+JQv1D33wkLZmUaD2bo0KIN7C C/8mbW/wJKrv5AoBG5WKhhPoBdZfS4FskmM2O0HGACUVq0MBB5o4HHbzG7WcZ39I+NpL 5T/l+/AL7EEO5c3EjCpNRZUKbKnmht2RY4qfDdA0LBa4Vxn8FxO6D7O9ypNUJDQbGWdv 7EDQ== X-Gm-Message-State: AOAM532aapLzA+5/InoC/tdEdYFOiXJZh7GygeY/sxtPnZLtxjvOno2+ iK5HKhUXilltMtQapz7WXtbLYOlYJnqgGXbdRoEu6WramM1M78XLz0q78j+DkRFtIznE7ukmVQG 9RMPBOm1a04IN07ZC37q6fLE= X-Received: by 2002:a05:6512:398a:b0:44a:56b9:c03e with SMTP id j10-20020a056512398a00b0044a56b9c03emr9618995lfu.553.1649345565231; Thu, 07 Apr 2022 08:32:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwRsXua89LYuxBL1W06y53JwMg2tuFJn2rau0bfoGf+PdhOeGaTn2SyXaCDS02bHxQgu3VvT+5/DPYDD8T3d5Y= X-Received: by 2002:a05:6512:398a:b0:44a:56b9:c03e with SMTP id j10-20020a056512398a00b0044a56b9c03emr9618979lfu.553.1649345565025; Thu, 07 Apr 2022 08:32:45 -0700 (PDT) MIME-Version: 1.0 References: <20220115194102.444140-1-lucp.at.work@gmail.com> <20220225163804.506142-1-lucp.at.work@gmail.com> In-Reply-To: From: David Marchand Date: Thu, 7 Apr 2022 17:32:33 +0200 Message-ID: Subject: Re: [PATCH v7] eal: fix rte_memcpy strict aliasing/alignment bugs To: "Ananyev, Konstantin" , Luc Pelletier Cc: "Richardson, Bruce" , "dev@dpdk.org" , "Li, Xiaoyun" , "stable@dpdk.org" , Aaron Conole , Owen Hilyard 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" 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 On Thu, Apr 7, 2022 at 5:24 PM David Marchand wrote: > > On Thu, Mar 10, 2022 at 3:55 PM Ananyev, Konstantin > wrote: > > > Calls to rte_memcpy for 1 < n < 16 could result in unaligned > > > loads/stores, which is undefined behaviour according to the C > > > standard, and strict aliasing violations. > > > > > > The code was changed to use a packed structure that allows aliasing > > > (using the __may_alias__ attribute) to perform the load/store > > > operations. This results in code that has the same performance as the > > > original code and that is also C standards-compliant. > > > > > > Fixes: d35cc1fe6a7a ("eal/x86: revert select optimized memcpy at run-time") Actually, looking again at the history, it fixes: Fixes: f5472703c0bd ("eal: optimize aligned memcpy on x86") I'll change before pushing. -- David Marchand