From: Boaz Harrosh <bharrosh@panasas.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML development, anyone?
Date: Sun, 12 Sep 2010 11:48:34 +0200 [thread overview]
Message-ID: <4C8CA1F2.1060802@panasas.com> (raw)
In-Reply-To: <4C8C8291.2040303@iki.fi>
On 09/12/2010 09:34 AM, Sakari Ailus wrote:
>> - Please send a detailed bug report about that data corruption so someone
>> can reproduce it. I'm not sure what block device you are using but it has
>> a bug. If you have a good version 2.6.27 and a bad version 2.6.28. It should
>> be easy to "git bisect" to the exact patch that broke the system, and should
>> be easy to fix. (Tell me if you need help, it's easy really)
>
> I did write about this back then but it seems no-one else had the same
> problem. It's one thing to find it and the other to fix it. My wild
> guess is that it's not a change to that actual driver that broke it.
>
A "git bisect" should be the best way to find what exactly broke it. If it's
not the driver then fine, that will be found as well.
Can you reliably reproduce the data corruption? If yes then a git bisect should
be easy. Please try to see what you can do?
Thanks
Boaz
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2010-09-12 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 22:17 [uml-devel] UML development, anyone? Sakari Ailus
2010-09-01 11:20 ` Boaz Harrosh
2010-09-12 7:34 ` Sakari Ailus
2010-09-12 9:48 ` Boaz Harrosh [this message]
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=4C8CA1F2.1060802@panasas.com \
--to=bharrosh@panasas.com \
--cc=sakari.ailus@iki.fi \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.