linux-kernel - Re: [RFC 0/2] virtio: provide a way for host to monitor critical events in the device

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, 24 Jul 2012 14:31:25 +0200
From:	Sasha Levin <levinsasha928@...il.com>
To:	Gleb Natapov <gleb@...hat.com>
CC:	rusty@...tcorp.com.au, mst@...hat.com, penberg@...nel.org,
	asias.hejun@...il.com, virtualization@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org, avi@...hat.com,
	anthony@...emonkey.ws, wency@...fujitsu.com
Subject: Re: [RFC 0/2] virtio: provide a way for host to monitor critical
 events in the device

On 07/24/2012 02:28 PM, Gleb Natapov wrote:
> On Tue, Jul 24, 2012 at 02:26:33PM +0200, Sasha Levin wrote:
>> On 07/24/2012 09:44 AM, Gleb Natapov wrote:
>>> On Mon, Jul 23, 2012 at 10:32:39PM +0200, Sasha Levin wrote:
>>>> As it was discussed recently, there's currently no way for the guest to notify
>>>> the host about panics. Further more, there's no reasonable way to notify the
>>>> host of other critical events such as an OOM kill.
>>>>
>>>> This short patch series introduces a new device named virtio-notifier which
>>>> does two simple things:
>>>>
>>>>  1. Provide a simple interface for the guest to notify the host of critical
>>> To get early OOPSes virtio will have to be compiled into the kernel. If
>>> your are so keen on using virtio for this though, why not just use
>>> dedicated virtio serial channel?
>>
>> Let's separate between having log for these events and receiving notifications about them.
>>
>> For the log part, I can already run a simple serial console to dump everything somewhere. I'm more concerned about having notifications about something critical happening when the guest is already up and running.
>>
> I am talking about notifications. Run your notification protocol over
> dedicated virtio-serial channel. Logs goes to virtio-console as you've
> said.

Ah, so just add another channel into virtio-serial to pass these notifications? Good idea - I'll look into it.


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