From: John Snow <jsnow@redhat.com>
To: qemu-block@nongnu.org
Cc: John Snow <jsnow@redhat.com>,
mark.cave-ayland@ilande.co.uk, armbru@redhat.com,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] atapi: fix NetBSD boot regression
Date: Mon, 9 Nov 2015 14:05:57 -0500 [thread overview]
Message-ID: <1447095959-10046-1-git-send-email-jsnow@redhat.com> (raw)
Marc noticed that a recent ATAPI permissions fix broke NetBSD 7.0's
installer ISO.
The problem is that it's meaningless to check for !(cmd->flags & nondata)
if the command isn't supported, since all unsupported commands have
_no_ flags. Effectively, all commands default to "Transfer Data" in our
model until we classify them otherwise.
This leads to a problem where we reject a zero byte BCL PIO command that
transfers no data, simply because we have no properties for the command
at all.
Getting an ATA rejection for this command greatly confuses NetBSD.
Correct behavior is to reject the command at the SCSI layer for being
unsupported.
________________________________________________________________________________
For convenience, this branch is available at:
https://github.com/jnsnow/qemu.git branch atapi-bclimit-netbsd
https://github.com/jnsnow/qemu/tree/atapi-bclimit-netbsd
This version is tagged atapi-bclimit-netbsd-v1:
https://github.com/jnsnow/qemu/releases/tag/atapi-bclimit-netbsd-v1
John Snow (2):
atapi: add byte_count_limit helper
atapi: Prioritize unknown cmd error over BCL error
hw/ide/atapi.c | 38 +++++++++++++++++++++++---------------
1 file changed, 23 insertions(+), 15 deletions(-)
--
2.4.3
next reply other threads:[~2015-11-09 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 19:05 John Snow [this message]
2015-11-09 19:05 ` [Qemu-devel] [PATCH 1/2] atapi: add byte_count_limit helper John Snow
2015-11-09 19:05 ` [Qemu-devel] [PATCH 2/2] atapi: Prioritize unknown cmd error over BCL error John Snow
2015-11-09 21:34 ` [Qemu-devel] [PATCH 0/2] atapi: fix NetBSD boot regression Mark Cave-Ayland
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=1447095959-10046-1-git-send-email-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-block@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).