From: Markus Armbruster <armbru@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>, Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Wed, 28 Jul 2010 13:22:49 +0200 [thread overview]
Message-ID: <m362zzdf5i.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <4C4EFB04.30901@codemonkey.ws> (Anthony Liguori's message of "Tue, 27 Jul 2010 10:28:04 -0500")
Anthony Liguori <anthony@codemonkey.ws> writes:
> On 07/27/2010 10:22 AM, Markus Armbruster wrote:
>> Kevin Wolf<kwolf@redhat.com> writes:
>>
>>
>>> Am 27.07.2010 15:00, schrieb Anthony Liguori:
>>>
>>>> On 07/27/2010 02:19 AM, Markus Armbruster wrote:
>>>>
>>>>> Anthony Liguori<anthony@codemonkey.ws> writes:
>>>>>
>>>>>
>>>>>
>>>>>> - any additional input on probed_raw?
>>>>>>
>>>>>>
>>>>> Isn't it a fait accompli? I stopped providing input when commit
>>>>> 79368c81 appeared.
>>>>>
>>>>>
>>>> No. 79368c81 was to close the security hole (and I do consider it a
>>>> security hole). But as I mentioned on the list, I'm also not satisfied
>>>> with it and that's why I proposed probed_raw. I was hoping to get a
>>>> little more input from those that objected to 79368c81 as to whether
>>>> probed_raw was more agreeable.
>>>>
>>> Actually I believe qraw is less agreeable. It just too much magic. You
>>> wouldn't expect that your raw images are turned into some other format
>>> that you can't mount or use with any other program any more.
>>>
>> I also dislike probed_raw, for the same reasons.
>>
>> Raw can't be probed safely, by its very nature. For historical reasons,
>> we try anyway. I think we should stop doing that, even though that
>> breaks existing use relying on the misfeature. Announce it now, spit
>> out scary warnings, kill it for good 1-2 releases later.
>>
>> If we're unwilling to do that, then I'd *strongly* prefer doing nothing
>> over silently messing with the raw writes to sector 0 (so does
>> Christoph, and he explained why).
>
> If we add docs/deprecated-features.txt, schedule removal for at least
> 1 year in the future, and put a warning in the code that prints
> whenever raw is probed, I think I could warm up to this.
>
> Since libvirt should be insulating users from this today, I think the
> fall out might not be terrible.
Okay, I'll prepare a patch.
next prev parent reply other threads:[~2010-07-28 11:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:28 KVM call agenda for July 27 Chris Wright
2010-07-26 22:28 ` Anthony Liguori
2010-07-26 23:28 ` Anthony Liguori
2010-07-27 0:13 ` Alex Williamson
2010-07-27 13:22 ` Jes Sorensen
2010-07-27 7:19 ` Markus Armbruster
2010-07-27 13:00 ` Anthony Liguori
2010-07-27 13:28 ` [Qemu-devel] " Kevin Wolf
2010-07-27 15:22 ` Markus Armbruster
2010-07-27 15:28 ` Anthony Liguori
2010-07-27 15:37 ` Daniel P. Berrange
2010-07-27 16:17 ` Avi Kivity
2010-07-27 16:24 ` Daniel P. Berrange
2010-07-27 16:29 ` Chris Wright
2010-07-27 16:32 ` Avi Kivity
2010-07-27 16:36 ` Chris Wright
2010-07-27 16:42 ` Avi Kivity
2010-07-27 17:01 ` Daniel P. Berrange
2010-07-27 17:37 ` Avi Kivity
2010-07-27 16:42 ` Daniel P. Berrange
2010-07-27 16:47 ` Avi Kivity
2010-07-27 16:48 ` Avi Kivity
2010-07-28 11:22 ` Markus Armbruster [this message]
2010-07-28 11:25 ` Kevin Wolf
2010-07-28 13:08 ` Markus Armbruster
2010-07-27 11:51 ` Daniel P. Berrange
2010-07-27 13:30 ` Anthony Liguori
2010-07-27 13:43 ` Cole Robinson
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=m362zzdf5i.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.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