From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, yanx.xia@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v1] lib/distributor: fix unaligned 128-bit write
Date: Tue, 20 Jul 2021 14:31:28 +0200 [thread overview]
Message-ID: <2095668.GCdfgjckzW@thomas> (raw)
In-Reply-To: <20210716133237.31464-1-david.hunt@intel.com>
16/07/2021 15:32, David Hunt:
> When the distributor sample app is built as a 32-bit app,
> the data buffer passed to find_match_vec can be unaligned,
> causing a segmentation fault due to writing a 128-bit value
> using _mm_store_si128(). 128-bit align the data being
> passed in so this does not happen.
>
> Fixes: 775003ad2f96 ("distributor: add new burst-capable library")
>
> Cc: stable@dpdk.org
>
> Signed-off-by: David Hunt <david.hunt@intel.com>
Applied, thanks
prev parent reply other threads:[~2021-07-20 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 13:32 [dpdk-stable] " David Hunt
2021-07-20 12:00 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2021-07-20 12:31 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2095668.GCdfgjckzW@thomas \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=yanx.xia@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).