From: Olivier MATZ <olivier.matz-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Neil Horman <nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Stefan Baranoff
<sbaranoff-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: Random mbuf corruption
Date: Tue, 24 Jun 2014 13:01:55 +0200 [thread overview]
Message-ID: <53A95AA3.90408@6wind.com> (raw)
In-Reply-To: <20140624104859.GA19229-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
Hi,
On 06/24/2014 12:48 PM, Neil Horman wrote:
> Sounds like it might be time to add in some poisoning options to the mbuf
> allocator.
Such option already exists: CONFIG_RTE_LIBRTE_MBUF_DEBUG and
RTE_LIBRTE_MEMPOOL_DEBUG will enable some runtime checks, at least
double free and buffer overflows.
Olivier
next prev parent reply other threads:[~2014-06-24 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHzKxpaxCbt9d+njdBBpwSy069zLfsOvQ5Dx0CzXLNVMKQ9AaQ@mail.gmail.com>
[not found] ` <CAHzKxpaNvZkH9h0kqYJd8VoYEXqBUfhSX9V_zUro2oX_-ioAAw@mail.gmail.com>
[not found] ` <CAHzKxpaNvZkH9h0kqYJd8VoYEXqBUfhSX9V_zUro2oX_-ioAAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-20 11:20 ` Random mbuf corruption Stefan Baranoff
[not found] ` <CAHzKxpZUOVKbCYTb66D8cQbm0ceSt7rfYo6VU3f2qhi2ZBvytQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-20 13:59 ` Paul Barrette
[not found] ` <53A43E5E.3030809-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2014-06-23 21:43 ` Stefan Baranoff
[not found] ` <CAHzKxpYaUhR5ti2EDZfj7jeu8pWxhnmWM+e2D20k01NHa_u85w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-24 8:05 ` Gray, Mark D
2014-06-24 10:48 ` Neil Horman
[not found] ` <20140624104859.GA19229-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-06-24 11:01 ` Olivier MATZ [this message]
[not found] ` <53A95AA3.90408-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-06-25 1:31 ` Stefan Baranoff
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=53A95AA3.90408@6wind.com \
--to=olivier.matz-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=nhorman-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=sbaranoff-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.