linux-kernel - Re: BUG kmalloc-64 (Not tainted): Poison overwritten

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHA+R7Mx7hQyLsLx68vV2Z7qGaRhGxPenX2NaY-cMKj6zfCP=Q@mail.gmail.com>
Date:	Tue, 25 Aug 2015 14:48:50 -0700
From:	Cong Wang <cwang@...pensource.com>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	virtualization@...ts.linux-foundation.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: BUG kmalloc-64 (Not tainted): Poison overwritten

On Tue, Aug 25, 2015 at 2:11 PM, Cong Wang <cwang@...pensource.com> wrote:
> Hi, Michael
>
> I just got the following kernel bug while working on Dave's net tree
> in a KVM guest. It looks like a bug in virtio.
>

Hmm, the stack trace is misleading, it could be caused by my own networking
code even though it doesn't show in dmesg. Anyway I can't reproduce it on the
clean -net tree.

I will let you know if it is really a bug.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/