linux-kernel - Re: kvm: unable to handle kernel NULL pointer dereference

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]

Message-ID: <20080629180203.GA9356@yamamaya.is-a-geek.org>
Date:	Sun, 29 Jun 2008 20:02:04 +0200
From:	Tobias Diedrich <ranma+kernel@...edrich.de>
To:	Chris Wright <chrisw@...s-sol.org>
Cc:	Avi Kivity <avi@...ranet.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Roedel, Joerg" <Joerg.Roedel@....com>
Subject: Re: kvm: unable to handle kernel NULL pointer dereference

Chris Wright wrote:
> * Tobias Diedrich (ranma+kernel@...edrich.de) wrote:
> > PM: Creating hibernation image: 
> > PM: Need to copy 126181 pages
> > PM: Normal pages needed: 126181 + 1024 + 38, available pages: 397721
> > x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> > svm_cpu_init: svm_data is NULL on 0
> 
> Yeah, this is broken.  What happens is:
> 
> suspend:
>   hardware_disable
>     svm_hardware_disable
>       kfree(svm_data)
>       per_cpu(svm_data) = NULL
> 
> resume:
>   hardware_enable
>     svm_hardware_enable
>       if(!svm_data) printk("svm_cpu_init: svm_data is NULL on 0")
> 
> at this point it is broken.
> 
> Same would happen on an SMP box by simply doing offline/online of a CPU.
> This is definitely busted, looking into a patch.

Any progress on this?

Thanks,

-- 
Tobias						PGP: http://9ac7e0bc.uguu.de
このメールは十割再利用されたビットで作られています。
--
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/