From: Andi Kleen <andi@firstfloor.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andi Kleen <andi@firstfloor.org>, linux-ide@vger.kernel.org
Subject: Re: libata exception handling messages at boot on qemu
Date: Tue, 8 Jan 2008 22:37:16 +0100 [thread overview]
Message-ID: <20080108213716.GB2403@one.firstfloor.org> (raw)
In-Reply-To: <20080108211931.4ef915fc@lxorguk.ukuu.org.uk>
On Tue, Jan 08, 2008 at 09:19:31PM +0000, Alan Cox wrote:
> > Since I assume that qemu code base is wide spread and if a workaround
> > is not too ugly I think it would be nice if the kernel handled that.
>
> Qemu behaves exactly the same way as a broken device in a situation where
> data corruption may occur. It would be extremely bad to remove sanity
> checking in storage subsystems just to deal with a silly bug in an
> emulator.
It could just a quirk e.g. matching on the ID string?
-Andi
next prev parent reply other threads:[~2008-01-08 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 19:23 libata exception handling messages at boot on qemu Andi Kleen
2008-01-08 20:17 ` Jim Paris
2008-01-08 21:04 ` Alan Cox
2008-01-08 21:21 ` Andi Kleen
2008-01-08 21:19 ` Alan Cox
2008-01-08 21:37 ` Andi Kleen [this message]
2008-01-08 21:40 ` Alan Cox
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=20080108213716.GB2403@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).