From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH rc8-mm1] hotfix libata-scsi corruption
Date: Tue, 22 Jan 2008 15:32:18 -0500 [thread overview]
Message-ID: <479652D2.10800@garzik.org> (raw)
In-Reply-To: <1201031028.3210.61.camel@localhost.localdomain>
James Bottomley wrote:
> Actually, I don't think it's a smaller I/O issue. The SMART protocol
> specifically mandates that the transfers for SMART READ DATA and SMART
> READ LOG shall be 512 bytes). However, the pio transfer routine does
> seem to be assuming sector alignment as well, which will be where your
> problems are coming from. I think we need to specify sector minimum
> alignment for ata (but not atapi, which has its own non sector size pio
> routine). How about the attached?
>
> We have to do this for all ATA devices, because they'll likely all
> support SMART, and SMART is defined to be a PIO command.
>
> James
>
> ---
>
> diff --git a/drivers/ata/libata-scsi.c b/drivers/ata/libata-scsi.c
> index 4bb268b..bc5cf6b 100644
> --- a/drivers/ata/libata-scsi.c
> +++ b/drivers/ata/libata-scsi.c
> @@ -824,9 +824,6 @@ static void ata_scsi_sdev_config(struct scsi_device *sdev)
> * requests.
> */
> sdev->max_device_blocked = 1;
> -
> - /* set the min alignment */
> - blk_queue_update_dma_alignment(sdev->request_queue, ATA_DMA_PAD_SZ - 1);
> }
>
> static void ata_scsi_dev_config(struct scsi_device *sdev,
> @@ -842,7 +839,14 @@ static void ata_scsi_dev_config(struct scsi_device *sdev,
> if (dev->class == ATA_DEV_ATAPI) {
> struct request_queue *q = sdev->request_queue;
> blk_queue_max_hw_segments(q, q->max_hw_segments - 1);
> - }
> +
> + /* set the min alignment */
> + blk_queue_update_dma_alignment(sdev->request_queue,
> + ATA_DMA_PAD_SZ - 1);
> + } else
> + /* ATA devices must be sector aligned */
> + blk_queue_update_dma_alignment(sdev->request_queue,
> + ATA_SECT_SIZE - 1);
>
> if (dev->flags & ATA_DFLAG_AN)
> set_bit(SDEV_EVT_MEDIA_CHANGE, sdev->supported_events);
ACK
Unlike ATAPI, ATA is indeed all 512-byte alignment transfers (_not_
sector size, which may or may not be 512 bytes)
Does this apply to libata? libata + jejb dma alignment patch?
What tree...
Jeff
next prev parent reply other threads:[~2008-01-22 20:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 17:11 [PATCH rc8-mm1] hotfix libata-scsi corruption Hugh Dickins
2008-01-22 17:29 ` James Bottomley
2008-01-22 18:36 ` Hugh Dickins
2008-01-22 19:43 ` James Bottomley
2008-01-22 20:20 ` Hugh Dickins
2008-01-22 22:12 ` James Bottomley
2008-01-22 22:59 ` Hugh Dickins
2008-01-22 23:19 ` James Bottomley
2008-01-22 23:58 ` Matt Mackall
2008-01-22 20:32 ` Jeff Garzik [this message]
2008-01-22 23:00 ` James Bottomley
2008-01-22 22:12 ` Alan Cox
2008-01-22 22:41 ` Hugh Dickins
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=479652D2.10800@garzik.org \
--to=jeff@garzik.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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