From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Paasch <christoph.paasch@gmail.com>
Cc: Christoph Paasch <christoph.paasch@uclouvain.be>,
"Michael S. Tsirkin" <mst@redhat.com>,
stable@kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: Kmemleak: false-positive in vring_add_indirect ?
Date: Mon, 07 Oct 2013 19:52:44 +1030 [thread overview]
Message-ID: <87siwdwi3f.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CALMXkpYyFwKtbyp2_yRfxt0_0HddfF+GJDw7y2CGArg9H+cFtQ@mail.gmail.com>
Christoph Paasch <christoph.paasch@gmail.com> writes:
> On Fri, Oct 4, 2013 at 1:59 AM, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Thanks! Does this work?
>>
>> virtio_ring: plug kmemleak false positive.
>
> Yes, it does work.
>
> Tested-by: Christoph Paasch <christoph.paasch@uclouvain.be>
>
> This patch should be sent to stable.
I disagree. Removing an annoying warning is not a fix.
Cheers,
Rusty.
prev parent reply other threads:[~2013-10-07 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 20:20 Kmemleak: false-positive in vring_add_indirect ? Christoph Paasch
2013-10-03 23:59 ` Rusty Russell
2013-10-04 7:23 ` Christoph Paasch
2013-10-07 9:22 ` Rusty Russell [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=87siwdwi3f.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=christoph.paasch@gmail.com \
--cc=christoph.paasch@uclouvain.be \
--cc=mst@redhat.com \
--cc=stable@kernel.org \
--cc=virtualization@lists.linux-foundation.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