DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Alexander Bechikov <asb.tyum@gmail.com>,
	Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH v3] mbuf: fix dump of dynamic fields and flags
Date: Wed, 24 Nov 2021 15:08:59 +0100	[thread overview]
Message-ID: <1791907.f4KDkszaHv@thomas> (raw)
In-Reply-To: <20211124125704.26054-1-olivier.matz@6wind.com>

24/11/2021 13:57, Olivier Matz:
> From: Alexander Bechikov <asb.tyum@gmail.com>
> 
> The dump of dynamic fields and flags fails if the shm is already
> allocated. Add a check to fix the issue.
> 
> Cc: stable@dpdk.org
> Fixes: d4902ed31c63 ("mbuf: check shared memory before dumping dynamic space")
> 
> Signed-off-by: Alexander Bechikov <asb.tyum@gmail.com>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>
> ---
> Hi Alexander,
> 
> Sorry for late feedback, I forgot to reply to your v2.
> I'm resending your fix with the 2 patches merged together, so it
> can be included in 21.11.

Applied for 21.11, thanks.




      reply	other threads:[~2021-11-24 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 11:11 [dpdk-dev] [PATCH] mbuf: Improved error message. Added check if shared memory already allocated Alexander Bechikov
2021-10-29  7:31 ` Olivier Matz
2021-10-29 19:35 ` [dpdk-dev] [PATCH v2 1/2] " Alexander Bechikov
2021-10-29 19:35   ` [dpdk-dev] [PATCH v2 2/2] mbuf: fix dump of dynamic fields and flags Alexander Bechikov
2021-11-24 12:57 ` [PATCH v3] " Olivier Matz
2021-11-24 14:08   ` 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=1791907.f4KDkszaHv@thomas \
    --to=thomas@monjalon.net \
    --cc=asb.tyum@gmail.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=stable@dpdk.org \
    /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).