From: Ewan Mellor <ewan@xensource.com>
To: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
Date: Wed, 24 May 2006 23:01:04 +0100 [thread overview]
Message-ID: <20060524220104.GA7657@leeni.uk.xensource.com> (raw)
In-Reply-To: <1148476190.7791.47.camel@localhost.localdomain>
On Wed, May 24, 2006 at 02:09:49PM +0100, Harry Butterworth wrote:
> > Modifying the ramdisk is not verboten,
> > but it is a right pain in the backside for everyone, particularly me because I
> > need to build a new one and upload it and all of its source (because of the
> > GPL) to xm-test.xensource.com.
>
> The current test is modifying the ramdisk to add `tee` (as well as fancy
> head which we don't need anymore).
>
> Are you going to accept the patch if it requires the addition of `tee`
> to the ramdisk? Or should I change the test to read the data back in
> domU---which I was specifically trying to avoid.
>
> The problem with reading the data back in domU after having written it
> is that it might mask bugs in the block driver. Reading the data back
> might cause it to be committed to the device where otherwise a bug might
> cause it to be lost.
I think that's a fair point, so yes, we'll have to rev the ramdisk anyway.
Ewan.
next prev parent reply other threads:[~2006-05-24 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 10:35 [PATCH] [XM-TEST] block device write verify test 2nd attempt Harry Butterworth
2006-05-23 11:40 ` Ewan Mellor
2006-05-23 12:35 ` Harry Butterworth
2006-05-24 10:20 ` Ewan Mellor
2006-05-24 11:08 ` Harry Butterworth
2006-05-24 12:37 ` Ewan Mellor
2006-05-24 13:09 ` Harry Butterworth
2006-05-24 22:01 ` Ewan Mellor [this message]
2006-05-24 9:52 ` Harry Butterworth
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=20060524220104.GA7657@leeni.uk.xensource.com \
--to=ewan@xensource.com \
--cc=harry@hebutterworth.freeserve.co.uk \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.