linux-kernel - Re: KVM guest-kernel panics double fault

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 10 Jan 2012 14:34:12 +0200
From:	Avi Kivity <avi@...hat.com>
To:	stephan.baerwolf@...ilmenau.de
CC:	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: KVM guest-kernel panics double fault

On 01/10/2012 02:17 PM, Stephan Bärwolf wrote:
> Hi, me again.
>
> Thank you for your instructions, I will send the patch right after this
> mail.
>
> On 01/10/12 11:31, Avi Kivity wrote:
> >> I prepare/adapt everything to the mentioned styles/policy.
> >> (I'll insert 2 additional ops for getting "cpuid" and "id of vcpu"...)
> > What do you mean by "id of vcpu"?
> I mean the number of the corresponding vcpu.
> (So mostly "vcpu->vcpu_id" ...)
> It is necessary for "pr_err_ratelimited"-complains, if cpuid-vendor is
> unknown ...
> ("Jan 10 12:14:55 thinkrat kernel: [ 4476.484359] kvm: 15680: cpu0
> unknown vendor - assuming intel")

It isn't worthwhile - just don't print the vcpu number (the task ID
contains enough information, and anyway this should be rare to the point
of never ever happening)

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
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/